Triple
T17620958
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chukchi language |
E429706
|
entity |
| Predicate | scriptAdoptedIn |
P45400
|
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: [Chukchi language, scriptAdoptedIn, 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scriptAdoptedIn Context triple: [Chukchi language, scriptAdoptedIn, 20th century]
-
A.
scriptAdaptationFrom
Indicates that a script is adapted or derived from a pre-existing source work (such as a book, play, or earlier script).
-
B.
scriptAncestor
chosen
Indicates that one script is an ancestor of another in a script family or derivation hierarchy, meaning the latter historically descends from or is derived from the former.
-
C.
adoptedInSession
Indicates that a proposal, decision, or measure was formally approved and adopted during a specific session or meeting.
-
D.
adoptedInPlace
Indicates that an adoption event occurred within or is associated with a specific place or location.
-
E.
adoptedBy
Indicates that an entity has been taken in and legally or formally accepted as a child, member, or responsibility by another entity.
- 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_69d889e37f308190a6aa0a69daff86c7 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46d36074481909ee79e238841edf2 |
completed | April 19, 2026, 5:50 a.m. |
| PD | Predicate disambiguation | batch_69e3cdd7da34819099bc9481c5a79bab |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 5:51 a.m.