Triple
T7696460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISO 15924 |
E174382
|
entity |
| Predicate | codeElementFormat |
P2202
|
FINISHED |
| Object | four-letter Latin alphabet 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 Latin alphabet code | Statement: [ISO 15924, codeElementFormat, four-letter Latin alphabet code]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: codeElementFormat Context triple: [ISO 15924, codeElementFormat, four-letter Latin alphabet code]
-
A.
syntaxStyle
Indicates the stylistic or structural conventions used in the form or arrangement of an expression, statement, or code.
-
B.
codeStandard
Indicates that an entity adheres to, complies with, or is governed by a specified coding or programming standard.
-
C.
codeType
chosen
Indicates the classification or category assigned to a particular code within a coding or encoding system.
-
D.
syntaxElement
Indicates a relationship where something functions as a syntactic unit or component within a larger grammatical or structural expression.
-
E.
codeFor
Indicates that one entity serves as the implementation, encoding, or programmatic representation for 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_69c6995a72cc8190998e56daa6f8e453 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c70402169481909b219dc5f4a64b9b |
completed | March 27, 2026, 10:26 p.m. |
| PD | Predicate disambiguation | batch_69c70165e78c8190bf6b3c34e243cb81 |
completed | March 27, 2026, 10:15 p.m. |
Created at: March 27, 2026, 4:03 p.m.