Triple
T27232803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cyrl |
E682198
|
entity |
| Predicate | scriptOriginRegion |
P410
|
FINISHED |
| Object | Eastern 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: Eastern Europe | Statement: [Cyrl, scriptOriginRegion, Eastern Europe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scriptOriginRegion Context triple: [Cyrl, scriptOriginRegion, Eastern Europe]
-
A.
sourceRegion
chosen
Indicates the geographic or spatial region from which something originates or is derived.
-
B.
scriptDirectionOrigin
Indicates the original writing direction (such as left-to-right or right-to-left) from which a script’s layout or orientation is derived.
-
C.
originalPlatformRegion
Indicates the geographic region or market in which a platform was originally launched or made available.
-
D.
registrationOrigin
Indicates the source or context from which a registration event was initiated or created.
-
E.
scriptOfOrigin
Indicates that one entity is the original writing system or script from which another script is derived or historically originates.
- 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_69eefacdad7881908b7bca61c90a1a1e |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f66c5c13808190887180099745673b |
completed | May 2, 2026, 9:27 p.m. |
| PD | Predicate disambiguation | batch_69f66abddc448190a488852f8abdeb2c |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 27, 2026, 9:46 a.m.