Triple
T9263624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NBA All-Star |
E222639
|
entity |
| Predicate | selectionUnit |
P16786
|
FINISHED |
| Object | individual player |
—
|
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: individual player | Statement: [NBA All-Star, selectionUnit, individual player]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: selectionUnit Context triple: [NBA All-Star, selectionUnit, individual player]
-
A.
selectionRegion
Indicates a relationship where a specific region or area is designated as the active selection within a larger space or context.
-
B.
selectionShow
Indicates that a particular selection or choice is being displayed or made visible.
-
C.
selectedTo
Indicates that one entity has been chosen or designated from a set of candidates to perform a role, receive something, or participate in an activity in relation to another entity.
-
D.
selectionRight
Indicates that one entity is chosen or designated as the correct or preferred option among a set of possible selections.
-
E.
selectionFrom
chosen
Indicates that one entity is chosen as a member or subset from a larger set or collection represented by another entity.
- 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_69ca841f2e808190a64f4c31903a1332 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd0719eee081909e21ecb9d6dd0b49 |
completed | April 1, 2026, 11:52 a.m. |
| PD | Predicate disambiguation | batch_69cc7a537bbc8190baee71f556e52a7b |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:32 p.m.