Triple
T7124725
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mech (historical name) |
E166030
|
entity |
| Predicate | hasReferentISO639_3Code |
P8719
|
FINISHED |
| Object | brx |
—
|
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: brx | Statement: [Mech (historical name), hasReferentISO639_3Code, brx]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReferentISO639_3Code Context triple: [Mech (historical name), hasReferentISO639_3Code, brx]
-
A.
hasISO6393Code
chosen
Indicates that a language or linguistic entity is associated with a specific ISO 639-3 three-letter language code.
-
B.
hasISO639_5Code
Indicates that a language or language group is associated with a specific ISO 639-5 code that identifies it within the ISO 639-5 language classification standard.
-
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.
ISO639-3CodeOfLanguage
Indicates that one entity is the ISO 639-3 three-letter language code assigned to the language represented by the other entity.
-
E.
ISO639-2Equivalent
Indicates that two language identifiers are equivalent according to the ISO 639-2 language code standard.
- 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_69c6888350588190870cd552b427a1cd |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e64c0f688190a9b7482d86c2f033 |
completed | March 27, 2026, 8:19 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c7289881909f3b533c384f9ed4 |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:44 p.m.