Triple
T38309515
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regor (cut-down) |
E1033645
|
entity |
| Predicate | hasArchitectureFamily |
P24956
|
FINISHED |
| Object | AMD K10 |
—
|
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: AMD K10 | Statement: [Regor (cut-down), hasArchitectureFamily, AMD K10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasArchitectureFamily Context triple: [Regor (cut-down), hasArchitectureFamily, AMD K10]
-
A.
hasArchitectureBy
Indicates that an entity’s architectural design was created or authored by a specified architect or architectural firm.
-
B.
usesArchitecture
chosen
Indicates that one entity is built, implemented, or operates according to the architectural style, framework, or design specified by another entity.
-
C.
hasSubArchitecture
Indicates that one architectural component or structure is a subordinate or constituent part of a larger overarching architecture.
-
D.
comparesArchitectureTo
Indicates that one entity evaluates or contrasts the structure, design, or architectural characteristics of another entity against a reference or alternative architecture.
-
E.
usesArchitectureComponent
Indicates that one entity employs or incorporates a specific architecture component as part of its structure, design, or implementation.
- 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_69f76e132c408190969b3d35c04b87ae |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69feb8e856d48190aa34ad8ee8376e1c |
completed | May 9, 2026, 4:32 a.m. |
| PD | Predicate disambiguation | batch_69feb82a2b6c8190a473cc25976897be |
completed | May 9, 2026, 4:29 a.m. |
Created at: May 3, 2026, 4:30 p.m.