Triple
T19749350
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | All-WNBA Team selection |
E474336
|
entity |
| Predicate | positionStructure |
P137180
|
FINISHED |
| Object | guards |
—
|
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: guards | Statement: [All-WNBA Team selection, positionStructure, guards]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionStructure Context triple: [All-WNBA Team selection, positionStructure, guards]
-
A.
encodingStructure
Indicates the structural scheme or format used to encode information or data.
-
B.
verticalStructure
Indicates a relationship where one entity is a structure that extends predominantly in the vertical direction relative to another reference or context.
-
C.
branchStructure
Indicates how the parts of a branching system are organized and connected relative to one another.
-
D.
lapStructure
Indicates that one entity forms a lap-like structural surface or support upon which another entity can rest or be positioned.
-
E.
levelStructure
Indicates that one entity defines or organizes the hierarchical or layered arrangement of another entity.
- 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_69d8e51940a0819087bd2996f98da668 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65296fa80819085aa4a18153531cf |
completed | April 20, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69e5305016e08190b9561a96baecb0b8 |
completed | April 19, 2026, 7:43 p.m. |
| PDg | Predicate description generation | batch_69e532bbedf081908d801600e2af94a7 |
completed | April 19, 2026, 7:53 p.m. |
Created at: April 10, 2026, 1:47 p.m.