Triple
T30685533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Malyn |
E781173
|
entity |
| Predicate | telecommunicationsCountry |
P170030
|
FINISHED |
| Object | Ukraine |
—
|
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: Ukraine | Statement: [Malyn, telecommunicationsCountry, Ukraine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: telecommunicationsCountry Context triple: [Malyn, telecommunicationsCountry, Ukraine]
-
A.
telecommunicationsRegulatorOfCountry
Indicates that an entity serves as the official telecommunications regulatory authority for a given country.
-
B.
continentCode
Indicates the standardized code assigned to the continent with which an entity is associated.
-
C.
numericCountryCode
Indicates that a country is associated with a specific numeric code that uniquely identifies it.
-
D.
mobileCountryCode
Indicates the numerical code that identifies the country associated with a mobile network or subscriber.
-
E.
coordinatesCountry
Indicates that one entity organizes, directs, or manages activities or operations within the specified country.
- F. None of above. chosen
Provenance (4 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_69f224a92f54819095499b4d32bd5134 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68b83da3881908f819b08aaba4ff2 |
completed | May 2, 2026, 11:40 p.m. |
| PD | Predicate disambiguation | batch_69f6861170d08190bb98be609d436f84 |
completed | May 2, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69f688034580819086a0f9100645f8ba |
completed | May 2, 2026, 11:25 p.m. |
Created at: April 29, 2026, 8:33 p.m.