Triple
T25819409
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fenian Ram |
E650358
|
entity |
| Predicate | engineerOfDesign |
P28525
|
FINISHED |
| Object | John Philip Holland |
—
|
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: John Philip Holland | Statement: [Fenian Ram, engineerOfDesign, John Philip Holland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: engineerOfDesign Context triple: [Fenian Ram, engineerOfDesign, John Philip Holland]
-
A.
engineeringDesign
Indicates the relationship in which an entity is responsible for planning, specifying, or creating the technical design of another entity (such as a system, component, or structure).
-
B.
designDiscipline
Indicates a relationship where an entity is associated with, categorized under, or practices a particular field or branch of design.
-
C.
mechanicalDesigner
Indicates that one entity is responsible for designing or engineering mechanical components, systems, or devices for another entity or project.
-
D.
designLead
chosen
Indicates that one entity serves as the primary designer or person in charge of leading the design work for another entity or project.
-
E.
designCheck
Indicates that an entity performs a review or verification of a design to ensure it meets specified requirements or standards.
- 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_69e7ab367fcc8190a5ff1e7f3da046a4 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6018f91248190985323d1a678e539 |
completed | May 2, 2026, 1:52 p.m. |
| PD | Predicate disambiguation | batch_69f5afec3e94819080d9ba86cf8c866e |
completed | May 2, 2026, 8:03 a.m. |
Created at: April 22, 2026, 7:28 a.m.