Triple
T35807103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boneyard Match |
E1035129
|
entity |
| Predicate | firstHeldOnDate |
—
|
GENERATED |
| Object | 2020-04-04 |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstHeldOnDate Context triple: [Boneyard Match, firstHeldOnDate, 2020-04-04]
-
A.
firstHeldAt
Indicates the initial time or event at which an entity was first held, possessed, or hosted.
-
B.
firstHeldAfter
Indicates that one entity’s first instance of holding or possessing something occurred later in time than another entity’s first such instance.
-
C.
firstHolderDate
chosen
Indicates the date on which an entity first became the holder or owner of another entity (e.g., an asset, title, or right).
-
D.
firstHeldFor
Indicates the initial time period or event during which an entity was first held, possessed, or hosted by another entity.
-
E.
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.
- F. None of above.
Provenance (1 batch)
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. |
Created at: May 3, 2026, 4:06 p.m.