Triple
T7399175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crnogorci |
E170701
|
entity |
| Predicate | autonymScript |
P63723
|
FINISHED |
| Object | Cyrillic |
—
|
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: Cyrillic | Statement: [Crnogorci, autonymScript, Cyrillic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: autonymScript Context triple: [Crnogorci, autonymScript, Cyrillic]
-
A.
autonymLanguageCode
Indicates that the associated language code is the one used by a language to refer to itself (its autonym).
-
B.
nativeNameScript
chosen
Indicates the writing system or script in which an entity’s native name is expressed.
-
C.
associatedLanguageScript
Indicates that there is a relationship between a language and the script or writing system used to represent it.
-
D.
hasEndonym
Indicates that an entity has a name or designation used by native speakers or within its own local language or community.
-
E.
hasEndonymLanguage
Indicates that the language specified is the one in which a name or term is expressed in its own native or local form.
- 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_69c68a5f04188190ac266569c9280347 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f24c1c208190a3d11e816888760d |
completed | March 27, 2026, 9:10 p.m. |
| PD | Predicate disambiguation | batch_69c6f0323b2c819098ab72c33e6d8534 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:09 p.m.