Triple
T7696491
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISO 15924 |
E174382
|
entity |
| Predicate | hasExampleCode |
P30248
|
FINISHED |
| Object | Latn |
—
|
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: Latn | Statement: [ISO 15924, hasExampleCode, Latn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasExampleCode Context triple: [ISO 15924, hasExampleCode, Latn]
-
A.
hasExample
Indicates that one entity serves as an instance, illustration, or concrete example of another entity.
-
B.
codeExample
chosen
Indicates that one entity provides a snippet or sample of source code that illustrates how to use, implement, or demonstrate another entity.
-
C.
hasCodeIn
Indicates that one entity is represented, defined, or implemented within the codebase or coding context of another entity.
-
D.
hasAwardedForExamples
Indicates that one entity has given an award to another entity specifically in recognition of certain examples or illustrative works.
-
E.
hasNonExample
Indicates that something is associated with an instance that explicitly does not satisfy or illustrate a given concept, rule, or category.
- 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.