Triple
T33501711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Travis Brickley |
E858004
|
entity |
| Predicate | fightsAtVenue |
P70420
|
FINISHED |
| Object | The Coliseum |
—
|
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: The Coliseum | Statement: [Travis Brickley, fightsAtVenue, The Coliseum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fightsAtVenue Context triple: [Travis Brickley, fightsAtVenue, The Coliseum]
-
A.
fightsAtLocation
chosen
Indicates that a fighting interaction between entities occurs at a specified location.
-
B.
playsInArenaLocatedIn
Indicates that an entity performs or participates in events within an arena that is geographically located in a specified place.
-
C.
fightsUsing
Indicates that one entity engages in combat or conflict by employing another entity as its weapon, tool, or method of fighting.
-
D.
notableFightSeries
Indicates that there is a recurring or thematically linked series of fights or battles associated with the subject.
-
E.
hasVenueFor
Indicates that one entity provides or serves as the location or setting where an event, activity, or function takes place for another 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_69f3497660508190a541826a81f7e9ab |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6e59b70d881908c64077ae3b24464 |
completed | May 3, 2026, 6:05 a.m. |
| PD | Predicate disambiguation | batch_69f6e3db74c081909a991309d835d477 |
completed | May 3, 2026, 5:57 a.m. |
Created at: May 1, 2026, 1:38 a.m.