Triple
T13317018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BUNCH |
E317211
|
entity |
| Predicate | hasMemberRole |
P161
|
FINISHED |
| Object | Control Data Corporation was a major mainframe manufacturer |
—
|
LITERAL FINISHED |
How this triple was built (1 step)
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: Control Data Corporation was a major mainframe manufacturer | Statement: [BUNCH, hasMemberRole, Control Data Corporation was a major mainframe manufacturer]
Provenance (2 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_69d806b4d62c81908d4ced1665414be5 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d990f9a384819085890e18255ee339 |
completed | April 11, 2026, 12:08 a.m. |
Created at: April 9, 2026, 9:29 p.m.