Triple
T26989082
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Choupette |
E679816
|
entity |
| Predicate | knownToTravelBy |
P15183
|
FINISHED |
| Object | private jet |
—
|
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: private jet | Statement: [Choupette, knownToTravelBy, private jet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: knownToTravelBy Context triple: [Choupette, knownToTravelBy, private jet]
-
A.
traveledToBy
Indicates that an entity has been traveled to or visited by another entity.
-
B.
travelsOn
chosen
Indicates that an entity moves or journeys using a particular route, path, or mode of transportation.
-
C.
traveledAs
Indicates that an entity moved from one place to another in the role, capacity, or identity specified by another entity (e.g., as a tourist, as a representative, as a refugee).
-
D.
coTraveler
Indicates that two or more entities are traveling together along (part of) the same journey or route.
-
E.
oftenTravelsTo
Indicates that one entity frequently goes to or visits another location or entity.
- 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_69eeeb5138ac8190b3c273ddc659a54f |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f65aa07c048190a5df30d53d8f0cf5 |
completed | May 2, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f659cc571c819097e51e531961d812 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 27, 2026, 6:50 a.m.