Triple
T19073239
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISO 843 |
E466843
|
entity |
| Predicate | scriptSource |
P134200
|
FINISHED |
| Object | Greek script |
—
|
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: Greek script | Statement: [ISO 843, scriptSource, Greek script]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scriptSource Context triple: [ISO 843, scriptSource, Greek script]
-
A.
scriptCode
Indicates that an entity is associated with a particular writing system or script, identified by a standardized script code.
-
B.
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).
-
C.
scriptText
Indicates that one entity contains or represents the textual content of a script associated with another entity.
-
D.
scriptElement
Indicates that one entity is a script element (such as code or instructions) that is embedded in or associated with another entity, typically a document or resource.
-
E.
scriptEditor
Indicates that an entity serves as the editor or editing environment used to create or modify a script.
- F. None of above. chosen
Provenance (4 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_69d8dd04f4488190b1121cc53ef2bfd6 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e2e1ce5881908367424c89d73feb |
completed | April 20, 2026, 8:25 a.m. |
| PD | Predicate disambiguation | batch_69e4b99f602881909eeb9c780597e0e6 |
completed | April 19, 2026, 11:16 a.m. |
| PDg | Predicate description generation | batch_69e4bfe8a06081909fd5c28a33e9f218 |
completed | April 19, 2026, 11:43 a.m. |
Created at: April 10, 2026, 12:04 p.m.