Triple
T1689942
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ray Allen |
E36527
|
entity |
| Predicate | holdsOrHeldRecord |
P2722
|
FINISHED |
| Object | NBA career leader in three-point field goals made |
—
|
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: NBA career leader in three-point field goals made | Statement: [Ray Allen, holdsOrHeldRecord, NBA career leader in three-point field goals made]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: holdsOrHeldRecord Context triple: [Ray Allen, holdsOrHeldRecord, NBA career leader in three-point field goals made]
-
A.
recordHeld
chosen
Indicates that one entity possesses or maintains a particular record associated with another entity or context.
-
B.
recordHeldFrom
Indicates that a record or position was held by an entity starting from a specified point in time.
-
C.
holdsIn
Indicates that a relationship, condition, or event is valid or occurs within a specified time interval or temporal context.
-
D.
heldAs
Indicates that one entity is kept, maintained, or regarded in a particular state, role, or condition by another entity.
-
E.
heldOn
Indicates that an event or activity takes place at a specific time, date, or occasion.
- 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_69a886151508819084fa7f1ce6e05577 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aaf3359ce48190803b322db8ad6027 |
completed | March 6, 2026, 3:31 p.m. |
| PD | Predicate disambiguation | batch_69aa61b71cec8190b273588051058ebd |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:29 p.m.