Triple
T2201264
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pawnee |
E50493
|
entity |
| Predicate | ISO639-3CodeOfLanguage |
P36930
|
FINISHED |
| Object | paw |
—
|
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: paw | Statement: [Pawnee, ISO639-3CodeOfLanguage, paw]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ISO639-3CodeOfLanguage Context triple: [Pawnee, ISO639-3CodeOfLanguage, paw]
-
A.
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.
-
B.
ISO639Macrolanguage
Indicates that a language variety is part of a broader ISO 639-defined macrolanguage grouping that encompasses multiple closely related individual languages.
-
C.
ISO639Scope
Indicates the classification of a language according to its scope, such as whether it represents an individual language, a macrolanguage, or a collection of languages.
-
D.
languageCodeISO639-2
Indicates that an entity is associated with a language identified by its ISO 639-2 three-letter code.
-
E.
ISO639_3Status
Indicates the classification or status assigned to a language according to the ISO 639-3 standard (e.g., active, extinct, historical, constructed).
- F. None of above. chosen
Provenance (4 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_69a88b044ab48190add007487680f009 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abbfa1b41c8190b0f7467d0dcdfbcd |
completed | March 7, 2026, 6:03 a.m. |
| PD | Predicate disambiguation | batch_69abbda706f4819094de73e1d1d1f539 |
completed | March 7, 2026, 5:54 a.m. |
| PDg | Predicate description generation | batch_69abbf35c994819088a093c412931de4 |
completed | March 7, 2026, 6:01 a.m. |
Created at: March 4, 2026, 7:46 p.m.