Triple
T7387448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marcian Hoff |
E170415
|
entity |
| Predicate | hasGivenField |
P65218
|
FINISHED |
| Object | integrated circuit design |
—
|
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: integrated circuit design | Statement: [Marcian Hoff, hasGivenField, integrated circuit design]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGivenField Context triple: [Marcian Hoff, hasGivenField, integrated circuit design]
-
A.
hasGiven
Indicates that one entity has transferred or presented something to another entity.
-
B.
hasInfield
Indicates that an entity possesses or includes a designated infield area, typically within a larger spatial or structural context.
-
C.
hasFieldName
Indicates that one entity is associated with, or identified by, a specific field name in a data structure or schema.
-
D.
hasFieldContribution
chosen
Indicates that an entity has made a contribution or provided input within a particular field, domain, or area of activity.
-
E.
hasFieldFormation
Indicates that an entity possesses or exhibits a particular field formation, such as a structured arrangement or configuration of fields.
- 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_69c68a5e2c9081909e713ce866e0060a |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f1f2bac481908ac74069182a4ce4 |
completed | March 27, 2026, 9:09 p.m. |
| PD | Predicate disambiguation | batch_69c6f0309cc88190b55d278969400294 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:08 p.m.