Triple
T7696558
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buhid |
E174384
|
entity |
| Predicate | ISO15924NumericCode |
P25981
|
FINISHED |
| Object | 372 |
—
|
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: 372 | Statement: [Buhid, ISO15924NumericCode, 372]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ISO15924NumericCode Context triple: [Buhid, ISO15924NumericCode, 372]
-
A.
ISO15924Status
Indicates the official status or classification of a script according to the ISO 15924 standard.
-
B.
hasISO15924Number
chosen
Indicates that an entity (a writing script) is associated with a specific numeric code defined by the ISO 15924 standard.
-
C.
scriptCodeISO15924
Indicates the script or writing system used to represent text, identified by its ISO 15924 code.
-
D.
UnicodeStandardVersionIntroduced
Indicates the specific version of the Unicode Standard in which a given character, feature, or property was first introduced.
-
E.
codingSystemType
Indicates the classification or category of coding system used to encode or represent information in a given context.
- 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.