Triple
T16756460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jordan FA Cup |
E407217
|
entity |
| Predicate | venueForFinal |
P12513
|
FINISHED |
| Object | major stadiums in Jordan (varies by season) |
—
|
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: major stadiums in Jordan (varies by season) | Statement: [Jordan FA Cup, venueForFinal, major stadiums in Jordan (varies by season)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: venueForFinal Context triple: [Jordan FA Cup, venueForFinal, major stadiums in Jordan (varies by season)]
-
A.
semiFinalVenue
Indicates the venue where a semifinal match or event takes place.
-
B.
finalReplayVenue
Indicates the venue where a final match is replayed after an initial final did not produce a decisive result.
-
C.
finalConcertLocation
Indicates the location where a concert or performance ultimately takes place, especially after any changes or planning stages.
-
D.
venue
Indicates the place or location where an event, activity, or interaction takes place.
-
E.
finalsLocation
chosen
Indicates the place where the final stage or concluding event of something (such as a competition or process) takes place.
- 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_69d8839174188190909f190097207065 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3abe831ec8190bac05b07db6153c1 |
completed | April 18, 2026, 4:06 p.m. |
| PD | Predicate disambiguation | batch_69e319cbd79c8190a03587a61c18bec0 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:21 a.m.