Triple
T36019444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TNA Legends Championship |
E1041941
|
entity |
| Predicate | bookingNature |
P2435
|
FINISHED |
| Object | scripted |
—
|
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: scripted | Statement: [TNA Legends Championship, bookingNature, scripted]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bookingNature Context triple: [TNA Legends Championship, bookingNature, scripted]
-
A.
reservationNear
Indicates that a reservation is located geographically close to a specified reference entity or place.
-
B.
containsNaturalPark
Indicates that one entity geographically includes or encompasses a natural park within its boundaries.
-
C.
hasNature
chosen
Indicates that something possesses, exhibits, or is characterized by a particular inherent quality, essence, or fundamental type.
-
D.
guidanceNature
Indicates the type or character of guidance provided in the relationship between entities (e.g., advisory, directive, supportive, or instructional).
-
E.
bookingModel
Indicates a relationship where an entity uses or is associated with a specific model or schema that defines how bookings are structured, processed, or represented.
- 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_69f76e2b981881908e4e160607fa82eb |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7ace21cf08190ad1d2f5335d03dd1 |
completed | May 3, 2026, 8:15 p.m. |
| PD | Predicate disambiguation | batch_69f7ab75387c819091afc3c2128eb903 |
completed | May 3, 2026, 8:09 p.m. |
Created at: May 3, 2026, 4:07 p.m.