Triple
T24822285
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CGS-EMU system |
E621092
|
entity |
| Predicate | usesDimensionSystem |
P52772
|
FINISHED |
| Object | CGS dimensions |
—
|
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: CGS dimensions | Statement: [CGS-EMU system, usesDimensionSystem, CGS dimensions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesDimensionSystem Context triple: [CGS-EMU system, usesDimensionSystem, CGS dimensions]
-
A.
dimensionSystem
chosen
Indicates a standardized framework or scheme used to define, measure, and relate dimensions within a given context.
-
B.
includesDimension
Indicates that one entity encompasses or contains a particular dimension or measurable aspect as part of its definition or structure.
-
C.
hasDimension
Indicates that an entity possesses a specific measurable extent or size along one or more axes (e.g., length, width, height).
-
D.
dimensionType
Indicates the specific kind or category of dimension that characterizes how something is measured or structured.
-
E.
hasIndividualDimension
Indicates that an entity possesses a specific, separately identifiable dimension or measurable extent as an individual attribute.
- 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_69e2fabfd4648190bd0e5c7f4dbb6cab |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f44a417a58819081777e18dda149fd |
completed | May 1, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69f442b8479c8190a7c8e416ac9e28a0 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 5:04 a.m.