Triple
T10140106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kirrin Island |
E226958
|
entity |
| Predicate | centralLocationInWork |
P18768
|
FINISHED |
| Object | Famous Five stories |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Famous Five stories | Statement: [Kirrin Island, centralLocationInWork, Famous Five stories]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centralLocationInWork Context triple: [Kirrin Island, centralLocationInWork, Famous Five stories]
-
A.
centralLocation
chosen
Indicates that one entity serves as the primary or central place associated with another entity.
-
B.
locationInWork
Indicates that one entity specifies the place or setting where another entity occurs, is situated, or takes place within a particular work (e.g., a scene’s location in a film or a chapter’s setting in a book).
-
C.
centralWork
Indicates that a particular work is the primary, most important, or focal work associated with an entity or context.
-
D.
centralIn
Indicates that one entity occupies a central or most important position within another entity, context, or structure.
-
E.
locationOfWork
Indicates the place or site where an entity performs its work or carries out its professional activities.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69ca8433ec308190b8b25a6fe359c34c |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cdeb2425008190a92c5148ed703d5c |
completed | April 2, 2026, 4:05 a.m. |
| PD | Predicate disambiguation | batch_69cd4ba4f5d88190ba68e63be10b08c7 |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:07 p.m.