Triple
T14757394
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Armn |
E346764
|
entity |
| Predicate | scriptISO15924Number |
P25981
|
FINISHED |
| Object | 230 |
—
|
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: 230 | Statement: [Armn, scriptISO15924Number, 230]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scriptISO15924Number Context triple: [Armn, scriptISO15924Number, 230]
-
A.
hasISO15924Number
chosen
Indicates that an entity (a writing script) is associated with a specific numeric code defined by the ISO 15924 standard.
-
B.
scriptCodeISO15924
Indicates the script or writing system used to represent text, identified by its ISO 15924 code.
-
C.
ISO15924Status
Indicates the official status or classification of a script according to the ISO 15924 standard.
-
D.
ISO639Language
Indicates that an entity is associated with a language identified or classified according to the ISO 639 language code standard.
-
E.
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.
- 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_69d822e8896c819091169882f9b20486 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dec7ef0fd48190bd4a8af128ef274c |
completed | April 14, 2026, 11:04 p.m. |
| PD | Predicate disambiguation | batch_69de8c02e5c08190943c27594026faf7 |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:30 a.m.