Triple
T25436470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CISC |
E637384
|
entity |
| Predicate | exampleArchitecture |
P159124
|
FINISHED |
| Object | System/360 |
—
|
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: System/360 | Statement: [CISC, exampleArchitecture, System/360]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exampleArchitecture Context triple: [CISC, exampleArchitecture, System/360]
-
A.
architectureName
Indicates the specific name or title assigned to an architecture.
-
B.
renderingArchitecture
Indicates the specific rendering system or framework used to generate visual output for a given entity or environment.
-
C.
architecturalConcept
Indicates that one entity represents or embodies an architectural concept in relation to another entity.
-
D.
architectureType
Indicates the specific style or category of architecture that characterizes or defines an entity.
-
E.
architecturalProject
Indicates that one entity is an architectural project associated with, created by, or undertaken for another entity.
- F. None of above. chosen
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_69e75db6c97081908178383fa632b193 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f6e0338c8190ace22e7a6239f68d |
completed | May 2, 2026, 1:06 p.m. |
| PD | Predicate disambiguation | batch_69f49377411c8190b2188de444d76795 |
completed | May 1, 2026, 11:50 a.m. |
| PDg | Predicate description generation | batch_69f497b8abb88190bb672cf6907c4b8d |
completed | May 1, 2026, 12:08 p.m. |
Created at: April 21, 2026, 1:59 p.m.