Triple
T12808277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asia/Ust-Nera |
E306200
|
entity |
| Predicate | ianaDatabaseFile |
P39070
|
FINISHED |
| Object | asia |
—
|
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: asia | Statement: [Asia/Ust-Nera, ianaDatabaseFile, asia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ianaDatabaseFile Context triple: [Asia/Ust-Nera, ianaDatabaseFile, asia]
-
A.
dataFile
chosen
Indicates a relationship where one entity serves as or is associated with a specific data file used, stored, or referenced by another entity.
-
B.
primaryDatabaseFormat
Indicates the main data storage format or structure used by a database as its default or principal representation.
-
C.
derby
Indicates a competitive match or contest, typically between closely linked or rival entities (such as teams from the same area or group).
-
D.
usedInDatabases
Indicates that something is employed or implemented within one or more database systems or database contexts.
-
E.
eraSystem
Indicates a temporal classification relationship where an entity is associated with a particular era or chronological system used to organize time.
- 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_69d7bdf46c448190b1faa55aaacb6317 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96e808130819080f404b3a7462c2e |
completed | April 10, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69d9640ed7448190b276e7fab649f7d2 |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:31 p.m.