Triple
T24266644
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rotuman people |
E604855
|
entity |
| Predicate | ISO639-3LanguageCode |
P36930
|
FINISHED |
| Object | rtm |
—
|
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: rtm | Statement: [Rotuman people, ISO639-3LanguageCode, rtm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ISO639-3LanguageCode Context triple: [Rotuman people, ISO639-3LanguageCode, rtm]
-
A.
ISO639-3CodeOfLanguage
chosen
Indicates that one entity is the ISO 639-3 three-letter language code assigned to the language represented by the other entity.
-
B.
ISO639-3Type
Indicates the classification type assigned to a language within the ISO 639-3 standard (e.g., living, extinct, ancient, constructed, or special).
-
C.
sharesISO639-3CodeWith
Indicates that two language entities share the same ISO 639-3 code, meaning they are treated as the same language in that coding system.
-
D.
ISO639Language
Indicates that an entity is associated with a language identified or classified according to the ISO 639 language code standard.
-
E.
ISO639-3ReferenceName
Indicates the standardized reference name assigned to a language in the ISO 639-3 coding system.
- 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_69e29544c29c8190b023606eafe5d36a |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28c6bfe68819084ec59235ae58ff1 |
completed | April 29, 2026, 10:55 p.m. |
| PD | Predicate disambiguation | batch_69f1c450aa508190bc9d372a5f6ee47a |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:06 a.m.