Triple
T31302647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lover Fest |
E798248
|
entity |
| Predicate | hadPlannedLeg |
P134005
|
FINISHED |
| Object | North America |
—
|
NE NERFINISHED |
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: North America | Statement: [Lover Fest, hadPlannedLeg, North America]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadPlannedLeg Context triple: [Lover Fest, hadPlannedLeg, North America]
-
A.
hasTourLeg
Indicates that a specific segment or leg is part of, or associated with, a larger tour or journey.
-
B.
hasPlannedTransportConnection
Indicates that there is an intended or scheduled transport link (e.g., route, service, or connection) planned to operate between the related entities.
-
C.
intendedFlightProfile
Indicates the planned or expected way an aircraft is supposed to fly a mission, including its route, altitude, speed, and other flight parameters.
-
D.
isFlownOn
Indicates that an entity (such as a person or object) travels or is transported using a particular aircraft or airline as the means of flight.
-
E.
hasPlannedPart
chosen
Indicates that one entity includes another entity as a component or segment within a planned or scheduled whole.
- 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_69f224e0bd4c8190aab9b29a73f7aa3c |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d1bf8cc8190a78dfa5ab00daf3a |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 9:14 p.m.