Triple
T821729
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roger Staubach |
E17761
|
entity |
| Predicate | businessCareer |
P20899
|
FINISHED |
| Object | real estate executive |
—
|
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: real estate executive | Statement: [Roger Staubach, businessCareer, real estate executive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: businessCareer Context triple: [Roger Staubach, businessCareer, real estate executive]
-
A.
careerStart
Indicates the point in time when an entity begins its professional career or main occupational activity.
-
B.
careerImpact
Indicates how one entity influences or changes another entity’s professional trajectory, opportunities, or outcomes.
-
C.
laterCareer
Indicates that the associated information or events pertain to a later stage or phase in an entity’s professional life or career trajectory.
-
D.
partOfCareer
Indicates that one entity represents a role, position, or period that forms a component or phase within another entity’s overall career.
-
E.
careerOPS
Indicates a relationship where an entity’s career on-base plus slugging (OPS) statistic is recorded or associated with that 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_69a4937bcaac8190a322524ac6f45a5a |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4ab976094819086d676404d745750 |
completed | March 1, 2026, 9:11 p.m. |
| PD | Predicate disambiguation | batch_69a4aa76a7808190ac7fd9ba1a4cebcb |
completed | March 1, 2026, 9:07 p.m. |
| PDg | Predicate description generation | batch_69a4ab9634948190b25ea1b2e34df87d |
completed | March 1, 2026, 9:11 p.m. |
Created at: March 1, 2026, 7:38 p.m.