Triple
T15838267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ETSI EN 302 307 |
E384036
|
entity |
| Predicate | definesFrameStructure |
P86856
|
FINISHED |
| Object | normal frame |
—
|
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: normal frame | Statement: [ETSI EN 302 307, definesFrameStructure, normal frame]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesFrameStructure Context triple: [ETSI EN 302 307, definesFrameStructure, normal frame]
-
A.
definesStructure
chosen
Indicates that one entity specifies or determines the organizational form, composition, or arrangement of another entity.
-
B.
encodingStructure
Indicates the structural scheme or format used to encode information or data.
-
C.
displayStructure
Indicates that one entity presents or reveals the internal organization, layout, or arrangement of another entity.
-
D.
viaStructure
Indicates that one entity is connected to or accessed through a particular structural element or medium.
-
E.
layerStructure
Indicates a relationship where one entity is organized in or assigned to a specific layer or hierarchical level within a structured system.
- 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_69d86da34c888190976e06c4019d415a |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e142e3d48c8190ad0d0af89d062101 |
completed | April 16, 2026, 8:13 p.m. |
| PD | Predicate disambiguation | batch_69e005418f588190824d91ff7974dada |
completed | April 15, 2026, 9:38 p.m. |
Created at: April 10, 2026, 4:49 a.m.