Triple
T35620671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CCIR System G |
E1029302
|
entity |
| Predicate | regionGroup |
P5147
|
FINISHED |
| Object | European 625-line systems |
—
|
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: European 625-line systems | Statement: [CCIR System G, regionGroup, European 625-line systems]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionGroup Context triple: [CCIR System G, regionGroup, European 625-line systems]
-
A.
regionalGrouping
chosen
Indicates that entities are organized or associated together based on shared geographic or regional characteristics.
-
B.
region1
Indicates that one entity is the first or primary region associated with, containing, or encompassing another entity.
-
C.
regionSub
Indicates that one region is a subregion or contained part of another, larger region.
-
D.
longitudeRegion
Indicates that an entity is located within or associated with a specific longitudinal region on the Earth’s surface.
-
E.
placeRegion
Indicates that a place is located within, or is part of, a larger geographic or administrative region.
- 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_69f76e0709408190bbe322bf1707ef6b |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ffdd05d1908190957deb11392f4595 |
completed | May 10, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69ffdc0d33c881908b3483bee8a96540 |
completed | May 10, 2026, 1:14 a.m. |
Created at: May 3, 2026, 4:05 p.m.