Triple
T8363484
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2017 NBA All-Star Game |
E197065
|
entity |
| Predicate | previousRecordPoints |
P82313
|
FINISHED |
| Object | 42 |
—
|
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: 42 | Statement: [2017 NBA All-Star Game, previousRecordPoints, 42]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousRecordPoints Context triple: [2017 NBA All-Star Game, previousRecordPoints, 42]
-
A.
positionOnPast
Indicates that one entity occupied a specific position or location relative to another entity at some point in the past.
-
B.
previousPeg
Indicates that one peg directly precedes another peg in a defined sequence or ordering.
-
C.
previousPlayer
Indicates that one player directly precedes another player in a defined turn order or sequence.
-
D.
previousGround
Indicates that one entity is the immediately preceding ground or surface state relative to another in a sequence or progression.
-
E.
previousLocationTime
Indicates the specific time at which an entity was located at its immediately preceding location before its current one.
- F. None of above. chosen
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_69ca82f2dbe48190aba982e75a0d94de |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb80768b208190a5f6c9e6cb6e7f30 |
completed | March 31, 2026, 8:06 a.m. |
| PD | Predicate disambiguation | batch_69cb70cd04b08190ab5f72afd22a7967 |
completed | March 31, 2026, 6:59 a.m. |
| PDg | Predicate description generation | batch_69cb76d823b08190a54fadb50660cda5 |
completed | March 31, 2026, 7:25 a.m. |
Created at: March 30, 2026, 6 p.m.