Triple
T18147601
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thomas Jerome Newton |
E434427
|
entity |
| Predicate | roleInWorldEnterprisesCorporation |
P124907
|
FINISHED |
| Object | founder |
—
|
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: founder | Statement: [Thomas Jerome Newton, roleInWorldEnterprisesCorporation, founder]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInWorldEnterprisesCorporation Context triple: [Thomas Jerome Newton, roleInWorldEnterprisesCorporation, founder]
-
A.
underlyingCompanyRole
Indicates the specific function, position, or responsibility an entity holds within or in relation to a company.
-
B.
roleInWorldTradeCenter
Indicates a person's specific role, position, or involvement in relation to the World Trade Center.
-
C.
inUniverseWorkplaceRole
chosen
Indicates that an entity holds a specific workplace role or job position within a fictional or narrative universe.
-
D.
roleInCompanyLifecycle
Indicates the specific function or responsibility an entity has at a particular stage of a company's lifecycle.
-
E.
roleInIndustry
Indicates the specific function, position, or capacity an entity holds within a particular industry or sector.
- 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_69d8b90aac308190801e2c57d8c5bfe5 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4de360ae88190abe1ed13243e9924 |
completed | April 19, 2026, 1:52 p.m. |
| PD | Predicate disambiguation | batch_69e43317d11c81908d1dc14921566b47 |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:29 a.m.