Triple
T35807105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boneyard Match |
E1035129
|
entity |
| Predicate | firstHeldLocation |
P8094
|
FINISHED |
| Object | Orlando, Florida |
E11265
|
NE 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: Orlando, Florida | Statement: [Boneyard Match, firstHeldLocation, Orlando, Florida]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstHeldLocation Context triple: [Boneyard Match, firstHeldLocation, Orlando, Florida]
-
A.
firstHeldAt
Indicates the initial time or event at which an entity was first held, possessed, or hosted.
-
B.
firstHeldApproximate
Indicates that an entity’s initial holding or possession of something is known only approximately in time or value, rather than with exact precision.
-
C.
firstLocation
chosen
Indicates the initial or primary place where an entity is situated, originates, or where an event or relationship begins.
-
D.
firstHeldAtVenue
Indicates that an event was initially held at a particular venue for the first time.
-
E.
firstHeldAs
Indicates the initial time or context in which an entity was first possessed, owned, or held by another entity.
- F. None of above.
Provenance (4 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_69f76e1762408190b885a8456862e372 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037ce70f54819082946dad8d380825 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a389170738c81908fbc6d15c66cca41 |
completed | June 22, 2026, 1:35 a.m. |
| PD | Predicate disambiguation | batch_6a037a069e6c8190857b611fffb7b867 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:06 p.m.