Triple
T35774783
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MCP |
E1034259
|
entity |
| Predicate | originCompany |
P37135
|
FINISHED |
| Object | Burroughs large systems division |
E80461
|
NE 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: Burroughs large systems division | Statement: [MCP, originCompany, Burroughs large systems division]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originCompany Context triple: [MCP, originCompany, Burroughs large systems division]
-
A.
originatingCompany
chosen
Indicates the company from which something (such as a product, document, transaction, or request) originally comes or is issued.
-
B.
parentCompanyOfOrigin
Indicates that one company is the original parent or source company from which another company was created, derived, or spun off.
-
C.
originalCompanyAbbreviation
Indicates that an abbreviation represents the shortened or initial-based form of an original company’s full name.
-
D.
employerOrigin
Indicates that an employer entity originates from, is based in, or was founded in a specified place or source.
-
E.
originalOrganization
Indicates the organization from which an entity (such as a person, document, or resource) initially originated or was first associated.
- F. None of above.
Provenance (4 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_69f76e14a1e081908eddd57bd6fdb3be |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037ce70f54819082946dad8d380825 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a38ae1447d481908da23274b4f4ef7d |
completed | June 22, 2026, 3:37 a.m. |
| PD | Predicate disambiguation | batch_6a037a069e6c8190857b611fffb7b867 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:06 p.m.