Triple
T2983744
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inari Sámi |
E80571
|
entity |
| Predicate | hasOrthographyStandardizedIn |
P7432
|
FINISHED |
| Object | 20th century |
—
|
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: 20th century | Statement: [Inari Sámi, hasOrthographyStandardizedIn, 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOrthographyStandardizedIn Context triple: [Inari Sámi, hasOrthographyStandardizedIn, 20th century]
-
A.
hasStandardOrthographySince
chosen
Indicates that a language or writing system has used a particular standardized orthography starting from a specified point in time.
-
B.
usesStandardOrthographyOf
Indicates that one entity writes or represents language according to the standard orthographic system defined for another entity.
-
C.
hasOfficialOrthography
Indicates that an entity has a formally recognized and standardized system for writing its language or name.
-
D.
hasRomanizationStandard
Indicates that an entity’s romanized form follows a specified romanization standard or system.
-
E.
hasStandardPronunciationBasedOn
Indicates that one entity’s standard or canonical pronunciation is determined or derived from another entity’s pronunciation.
- 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_69ad8b15f6ac8190be5fd16a33edcb4f |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad99c481fc81909971c96352a881b4 |
completed | March 8, 2026, 3:46 p.m. |
| PD | Predicate disambiguation | batch_69ad9611fc348190a5d17d237f653f60 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:59 p.m.