Triple
T25068421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mictlan |
E627844
|
entity |
| Predicate | requiresJourneyOf |
P163672
|
FINISHED |
| Object | soul |
—
|
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: soul | Statement: [Mictlan, requiresJourneyOf, soul]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresJourneyOf Context triple: [Mictlan, requiresJourneyOf, soul]
-
A.
requiredTo
Indicates that one entity has an obligation or necessity to perform an action or satisfy a condition in relation to another entity or context.
-
B.
requiresJudgeToBe
Indicates that a situation, action, or process necessitates the judge to possess or be in a specific state, role, or condition.
-
C.
requiresFerries
Indicates that traveling between two locations involves or depends on the use of one or more ferries.
-
D.
requiresSameItinerary
Indicates that two or more entities must follow an identical travel plan or sequence of itinerary segments.
-
E.
requiresInitiationIn
Indicates that one entity must be initiated, started, or activated within the context, scope, or environment defined by another entity.
- 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_69e2ff2d71dc8190b4758e57d643cbe4 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f6397b64f881909d811225e57aac5e |
completed | May 2, 2026, 5:50 p.m. |
| PD | Predicate disambiguation | batch_69f63706b6008190993577193c85ff50 |
completed | May 2, 2026, 5:40 p.m. |
| PDg | Predicate description generation | batch_69f638d029148190877c103f0eeaf147 |
completed | May 2, 2026, 5:48 p.m. |
Created at: April 18, 2026, 6:10 a.m.