Triple
T37164376
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DVB-NGH |
E920754
|
entity |
| Predicate | regionOfStandardization |
P34987
|
FINISHED |
| Object | Europe |
—
|
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: Europe | Statement: [DVB-NGH, regionOfStandardization, Europe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionOfStandardization Context triple: [DVB-NGH, regionOfStandardization, Europe]
-
A.
countryOfStandardization
Indicates that a given standard, specification, or norm is officially established, adopted, or primarily recognized within a particular country.
-
B.
regionStandard
chosen
Indicates that something conforms to, is defined by, or is governed according to the official standards or norms of a particular region.
-
C.
isPartOfStandardizationSystem
Indicates that something belongs to, or is included within, a defined standardization framework, scheme, or system.
-
D.
standardizationScope
Indicates the extent or domain within which a standard or standardization effort is intended to apply or be enforced.
-
E.
regionallyRecognizedBy
Indicates that an entity is officially or commonly acknowledged within a specific geographic region by a particular authority, organization, or community.
- 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_69f76ea0429081908c711b55599eac3c |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a00512437d48190ad20324968ead5f4 |
completed | May 10, 2026, 9:34 a.m. |
| PD | Predicate disambiguation | batch_6a0050227350819099f41369c3d168be |
completed | May 10, 2026, 9:30 a.m. |
Created at: May 3, 2026, 4:15 p.m.