Triple
T14603811
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Falkor |
E342773
|
entity |
| Predicate | canTravel |
P74272
|
FINISHED |
| Object | through the skies of Fantastica |
—
|
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: through the skies of Fantastica | Statement: [Falkor, canTravel, through the skies of Fantastica]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canTravel Context triple: [Falkor, canTravel, through the skies of Fantastica]
-
A.
travelCapability
chosen
Indicates the ability or capacity of an entity to move or be transported from one location to another.
-
B.
travelsOn
Indicates that an entity moves or journeys using a particular route, path, or mode of transportation.
-
C.
allowsTravelAcross
Indicates that one entity enables or permits movement or passage from one side or location to another across a separating space or boundary.
-
D.
coTraveler
Indicates that two or more entities are traveling together along (part of) the same journey or route.
-
E.
travelMechanic
Indicates the method or system by which movement or travel between locations is carried out.
- 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_69d822dec68081908c2553145c4051dc |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb43a1bb48190bf520cb961f15b5e |
completed | April 14, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69de656f9f4c81909f815b6629a9ee39 |
completed | April 14, 2026, 4:03 p.m. |
Created at: April 10, 2026, 1:25 a.m.