Triple
T17271150
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cracker Line |
E419260
|
entity |
| Predicate | keyEngineer |
P616
|
FINISHED |
| Object | William F. Smith |
—
|
NE NERFINISHED |
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: William F. Smith | Statement: [Cracker Line, keyEngineer, William F. Smith]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyEngineer Context triple: [Cracker Line, keyEngineer, William F. Smith]
-
A.
chiefEngineer
chosen
Indicates that one entity serves as the primary or lead engineer responsible for overseeing engineering activities for another entity.
-
B.
engineeringRole
Indicates that an entity holds or is associated with a role or position in the field of engineering.
-
C.
keyDesigner
Indicates that an entity serves as the primary or lead designer responsible for creating or shaping another entity.
-
D.
key
Indicates that one entity functions as a key (literal or metaphorical) that unlocks, enables access to, or provides a crucial solution or control over another entity.
-
E.
keyProject
Indicates that an entity is a primary or strategically important project for another entity (such as an organization, person, or portfolio).
- 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_69d886da626481908a14ce7830329a35 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42f4a3c4c81908a28c9f8bdf648ca |
completed | April 19, 2026, 1:26 a.m. |
| PD | Predicate disambiguation | batch_69e3832c3b98819091967ac7e91ba316 |
completed | April 18, 2026, 1:12 p.m. |
Created at: April 10, 2026, 5:40 a.m.