Triple
T28041762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OIOI |
E708560
|
entity |
| Predicate | hasWritingSystemInLogo |
P26603
|
FINISHED |
| Object | Latin alphabet |
—
|
NE NERFINISHED |
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 alphabet | Statement: [OIOI, hasWritingSystemInLogo, Latin alphabet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWritingSystemInLogo Context triple: [OIOI, hasWritingSystemInLogo, Latin alphabet]
-
A.
hasOfficialWritingSystem
Indicates that an entity (typically a language) is associated with a formally recognized and standardized writing system used for official or standard purposes.
-
B.
haveWritingSystemsForSomeMembers
Indicates that at least some members of a group or category possess or use one or more writing systems.
-
C.
hasWritingSystemForMajorLanguage
Indicates that there exists a writing system used to represent a major language associated with the given entity.
-
D.
writingSystemUsedIn
chosen
Indicates that a particular writing system is employed for written communication within a given language, region, or context.
-
E.
usesLogogramsFrom
Indicates that one writing system or notation incorporates or employs logographic characters originating from another system.
- 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_69ef9b6cf538819094a633ffa67afec1 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f64dbbaefc8190952b8320bf4397d8 |
completed | May 2, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f64cacd2c08190aed8a1761d0da679 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 27, 2026, 8:26 p.m.