Triple
T14287691
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Matt Smith |
E354216
|
entity |
| Predicate | formerCareerAspiration |
P104631
|
FINISHED |
| Object | professional footballer |
—
|
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: professional footballer | Statement: [Matt Smith, formerCareerAspiration, professional footballer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerCareerAspiration Context triple: [Matt Smith, formerCareerAspiration, professional footballer]
-
A.
plannedCareer
Indicates that an individual has chosen and intends to pursue a specific career path.
-
B.
laterCareer
Indicates that the associated information or events pertain to a later stage or phase in an entity’s professional life or career trajectory.
-
C.
occupationAspiration
chosen
Indicates a person's desired or intended future occupation or career goal.
-
D.
managedCareerOf
Indicates that one entity was responsible for overseeing, directing, or handling the professional career of another entity.
-
E.
targetCareer
Indicates that one entity is the intended or pursued career or professional goal of 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_69d8278e17088190b328c5a9d4be74ff |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de698023288190b1d705235c2b2ca3 |
completed | April 14, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69de2a88446481909cd526da97a3b70f |
completed | April 14, 2026, 11:52 a.m. |
Created at: April 10, 2026, 1:11 a.m.