Triple
T18558204
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ignatian Way |
E453559
|
entity |
| Predicate | hasStageStructure |
P132151
|
FINISHED |
| Object | multi-stage route |
—
|
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: multi-stage route | Statement: [Ignatian Way, hasStageStructure, multi-stage route]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStageStructure Context triple: [Ignatian Way, hasStageStructure, multi-stage route]
-
A.
hasStationStructure
Indicates that an entity possesses or is associated with a particular station-related physical structure.
-
B.
hasStageType
Indicates that an entity is associated with, or classified by, a specific type or category of stage within a process, lifecycle, or workflow.
-
C.
hasFormationStage
Indicates that an entity is associated with a particular stage or phase in its formation or development process.
-
D.
hasHumanStructure
Indicates that one entity possesses or exhibits a structural form or organization characteristic of humans.
-
E.
hasStageRole
Indicates that an entity performs or holds a specific role or character in a staged performance or theatrical production.
- F. None of above. chosen
Provenance (4 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_69d8d388b0c881908e610a1c45b52640 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e53808028c8190825630525d84a29b |
completed | April 19, 2026, 8:16 p.m. |
| PD | Predicate disambiguation | batch_69e469e274a48190a570b25cfef4d890 |
completed | April 19, 2026, 5:36 a.m. |
| PDg | Predicate description generation | batch_69e46d2b93bc8190a6070018d7046547 |
completed | April 19, 2026, 5:50 a.m. |
Created at: April 10, 2026, 11:41 a.m.