Triple
T195002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Larry Bird |
E3798
|
entity |
| Predicate | frontOfficePosition |
P3459
|
FINISHED |
| Object | team president |
—
|
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: team president | Statement: [Larry Bird, frontOfficePosition, team president]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: frontOfficePosition Context triple: [Larry Bird, frontOfficePosition, team president]
-
A.
front
Indicates that one entity is located directly before or facing another entity along a primary viewing or movement direction.
-
B.
leftOffice
Indicates that an entity ceased holding or performing the duties of a particular office or position.
-
C.
frontType
Indicates the type or category of a front (e.g., boundary or leading side) that one entity presents or forms relative to another.
-
D.
leadershipPosition
chosen
Indicates that one entity holds a role of authority, guidance, or decision-making responsibility over others within an organization, group, or context.
-
E.
frontLine
Indicates that an entity is positioned at or associated with the foremost or primary line of engagement, activity, or defense relative to others.
- 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_69a2548debd48190ae3a06d6e65b53c6 |
completed | Feb. 28, 2026, 2:35 a.m. |
| NER | Named-entity recognition | batch_69a25969425081908e178db8ba4631c2 |
completed | Feb. 28, 2026, 2:56 a.m. |
| PD | Predicate disambiguation | batch_69a25677da14819094cd02868fd30c83 |
completed | Feb. 28, 2026, 2:44 a.m. |
Created at: Feb. 28, 2026, 2:41 a.m.