Triple
T7286298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nbat |
E163876
|
entity |
| Predicate | scriptCodeType |
P9329
|
FINISHED |
| Object | four-letter code |
—
|
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: four-letter code | Statement: [Nbat, scriptCodeType, four-letter code]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scriptCodeType Context triple: [Nbat, scriptCodeType, four-letter code]
-
A.
scriptType
Indicates the classification or category of a script, specifying what kind of script it is (e.g., its format, purpose, or scripting language type).
-
B.
scriptCode
chosen
Indicates that an entity is associated with a particular writing system or script, identified by a standardized script code.
-
C.
codeType
Indicates the classification or category assigned to a particular code within a coding or encoding system.
-
D.
scriptVariantLanguage
Indicates that a language is a variant distinguished by its writing system or script from another, related language form.
-
E.
scriptCodeContext
Indicates that a script is written or executed within a particular code context or environment.
- 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_69c6886093b88190a254b1ce6db8bae7 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6eb532adc8190bcbbf31bb54383fb |
completed | March 27, 2026, 8:40 p.m. |
| PD | Predicate disambiguation | batch_69c6e76c5fbc8190b378830082f11cb0 |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 2:59 p.m.