Triple
T1380975
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISO/IEC 8859-1 |
E29335
|
entity |
| Predicate | includesScript |
P5713
|
FINISHED |
| Object | Latin 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: Latin script | Statement: [ISO/IEC 8859-1, includesScript, Latin script]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesScript Context triple: [ISO/IEC 8859-1, includesScript, Latin script]
-
A.
containsScript
chosen
Indicates that one entity includes or embeds the script of another entity within it.
-
B.
relatedToScript
Indicates a general association or connection between an entity and a script, without specifying the exact nature of that relationship.
-
C.
scriptUsedCurrently
Indicates that a particular writing system or script is the one presently in use for a given language, text, or context.
-
D.
sisterScript
Indicates that two writing systems are closely related variants derived from a common ancestral script or design.
-
E.
scriptIndependent
Indicates that the relationship or action holds regardless of the writing system or script used to represent the entities involved.
- 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_69a498d883a48190bfdca525296ef7ee |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c31b176c8190a896183140c5c8be |
completed | March 1, 2026, 10:52 p.m. |
| PD | Predicate disambiguation | batch_69a4befe343c81909f758440a531b5be |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:59 p.m.