Triple
T15999531
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GD-ROM |
E388059
|
entity |
| Predicate | dataLayerType |
P69308
|
FINISHED |
| Object | single-layer |
—
|
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: single-layer | Statement: [GD-ROM, dataLayerType, single-layer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataLayerType Context triple: [GD-ROM, dataLayerType, single-layer]
-
A.
dataTypes
Indicates that one entity specifies or defines the kinds or formats of data that are valid or expected for another entity.
-
B.
datumType
Indicates the specific kind or category of data that characterizes or classifies a datum.
-
C.
layerType
chosen
Indicates the specific kind or category of layer that an entity belongs to or is classified as.
-
D.
dataBusType
Indicates the type or category of data bus used to transfer data between components or systems.
-
E.
logicalType
Indicates that one entity is classified as a logical type or category used to define or constrain the logical behavior or interpretation of another entity.
- 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_69d86daa562c81908aacc179c0fe8fb5 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e173b3bf6c81909230170e833d7ce7 |
completed | April 16, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69e142dc081c819082527e3fa8773460 |
completed | April 16, 2026, 8:13 p.m. |
Created at: April 10, 2026, 4:55 a.m.