Triple
T18205998
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tit-Bits |
E435904
|
entity |
| Predicate | positionInCareerOf |
P73957
|
FINISHED |
| Object | early success of George Newnes |
—
|
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: early success of George Newnes | Statement: [Tit-Bits, positionInCareerOf, early success of George Newnes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInCareerOf Context triple: [Tit-Bits, positionInCareerOf, early success of George Newnes]
-
A.
partOfCareer
Indicates that one entity represents a role, position, or period that forms a component or phase within another entity’s overall career.
-
B.
placeInCareer
chosen
Indicates the specific role, position, or stage an entity occupies within a person’s professional career.
-
C.
positionInWork
Indicates the specific role, rank, or placement an entity holds within a larger work or structured composition.
-
D.
positionInIndustry
Indicates the role, rank, or standing that an entity holds within a particular industry or sector.
-
E.
managedCareerOf
Indicates that one entity was responsible for overseeing, directing, or handling the professional career 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_69d8b90dba6481908e119eb9aa4ca0cb |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4e2234b988190bbe2c2164d61f65f |
completed | April 19, 2026, 2:09 p.m. |
| PD | Predicate disambiguation | batch_69e4332155d88190b106d0dceb4554af |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:32 a.m.