Triple
T28771515
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SH-3 |
E726423
|
entity |
| Predicate | hasPipelineType |
P120165
|
FINISHED |
| Object | RISC pipeline |
—
|
LITERAL 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: RISC pipeline | Statement: [SH-3, hasPipelineType, RISC pipeline]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPipelineType Context triple: [SH-3, hasPipelineType, RISC pipeline]
-
A.
hasPipeline
Indicates that one entity possesses, contains, or is associated with a pipeline used to transport or process something.
-
B.
typeOfPipeline
chosen
Indicates the specific category or kind of pipeline that an entity belongs to or represents.
-
C.
hasPipelineConnection
Indicates that one entity is linked to another via a pipeline through which materials, fluids, or data can flow.
-
D.
hasPipelineTerminal
Indicates that one entity possesses, contains, or is associated with a pipeline terminal as part of its infrastructure or connections.
-
E.
hasPoolType
Indicates that an entity’s swimming pool possesses a specific type or classification (e.g., indoor, outdoor, heated).
- 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_69f03199997c8190b6ae43fb19312443 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c2198208190a3954086c22cfcbf |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 6:16 a.m.