Triple
T36987757
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kingmambo |
E915008
|
entity |
| Predicate | studCareerLength |
P19680
|
FINISHED |
| Object | approximately 20 years |
—
|
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: approximately 20 years | Statement: [Kingmambo, studCareerLength, approximately 20 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: studCareerLength Context triple: [Kingmambo, studCareerLength, approximately 20 years]
-
A.
timeInCareer
Indicates the point or duration within an entity’s professional or occupational trajectory at which a related event, status, or condition occurs.
-
B.
studCareerStartYear
Indicates the calendar year in which a student's academic or educational career formally began.
-
C.
studCareerBegan
Indicates that a student's professional or academic career started at a specified time or institution.
-
D.
workYear
Indicates the specific year or span of years during which an entity (such as a person or organization) was engaged in work or employment.
-
E.
occupationDuration
chosen
Indicates the length of time an entity holds or has held a particular occupation or role.
- 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_69f76e8dd0408190b8b46da118ea5128 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb154c0fe08190a2e41e7a29b6055f |
completed | May 6, 2026, 10:17 a.m. |
| PD | Predicate disambiguation | batch_69f9fecc005c8190be082a8689193745 |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 3, 2026, 4:14 p.m.