Triple
T20462917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PG-13 |
E501971
|
entity |
| Predicate | positionOfPersonReferredTo |
P125178
|
FINISHED |
| Object | small forward |
—
|
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: small forward | Statement: [PG-13, positionOfPersonReferredTo, small forward]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionOfPersonReferredTo Context triple: [PG-13, positionOfPersonReferredTo, small forward]
-
A.
positionMentioned
chosen
Indicates that a specific position, role, or location is explicitly referenced or mentioned in relation to an entity or event.
-
B.
positionOften
Indicates that one entity frequently holds, occupies, or is located at a particular position relative to another entity or context.
-
C.
refersToPerson
Indicates that one entity is making reference to, mentioning, or pointing specifically to a particular person.
-
D.
positionDescribed
Indicates that a position, location, or spatial arrangement of an entity is explicitly specified or characterized, typically in descriptive terms.
-
E.
locationPosed
Indicates that an entity is positioned or situated at a specific location.
- 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_69e0b4ad4940819098cf2ff6413574e5 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e696a761648190b24cf4bb90a8abb1 |
completed | April 20, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69e57679eb40819086142df3e39c928e |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 16, 2026, 11:33 a.m.