Triple
T35736847
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unisys ClearPath MCP systems |
E1032911
|
entity |
| Predicate | architectureOrigin |
P61698
|
FINISHED |
| Object | Burroughs large systems architecture |
—
|
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: Burroughs large systems architecture | Statement: [Unisys ClearPath MCP systems, architectureOrigin, Burroughs large systems architecture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: architectureOrigin Context triple: [Unisys ClearPath MCP systems, architectureOrigin, Burroughs large systems architecture]
-
A.
architectOrigin
Indicates that an architect originally comes from, or is associated with, a particular place or region.
-
B.
architecturalOrigin
chosen
Indicates the place, style, or tradition from which an architectural work or design originates.
-
C.
buildingArchitectOfOriginal
Indicates that an entity is the architect responsible for the original design of a particular building.
-
D.
constructionOrigin
Indicates the source, cause, or initiating factor from which a construction or building project originates.
-
E.
architectureName
Indicates the specific name or title assigned to an architecture.
- 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_69f76e10e59081908d81ad9ce22f40b6 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fcd867f36081908c88c55a6a1404c1 |
completed | May 7, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f47b188190b4cf4b4c748d9d03 |
completed | May 7, 2026, 5:55 p.m. |
Created at: May 3, 2026, 4:05 p.m.