Triple
T8358201
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Six Flags Over Texas |
E196731
|
entity |
| Predicate | annualAttendance |
P38405
|
FINISHED |
| Object | over 2 million visitors (approximate) |
—
|
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: over 2 million visitors (approximate) | Statement: [Six Flags Over Texas, annualAttendance, over 2 million visitors (approximate)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: annualAttendance Context triple: [Six Flags Over Texas, annualAttendance, over 2 million visitors (approximate)]
-
A.
recordAttendanceYear
Indicates that an entity’s attendance is recorded or tracked for a specific calendar or academic year.
-
B.
annualVisitation
chosen
Indicates a recurring visit or attendance that takes place once every year between the related entities.
-
C.
attendance
Indicates the relationship between an event and the people who are present at or participate in that event.
-
D.
annualPractice
Indicates that an action, event, or behavior occurs as a recurring practice on a yearly basis.
-
E.
laterAttends
Indicates that one entity attends an event or place at a time later than another referenced attendance.
- 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_69ca82f08b348190bfb7881944bbff6f |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb806fa5c88190b23b6b3ee9d6ec6d |
completed | March 31, 2026, 8:06 a.m. |
| PD | Predicate disambiguation | batch_69cb70ca25548190b0f90c5384e3fb3c |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 5:59 p.m.