Triple
T37748678
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | E6 |
E940916
|
entity |
| Predicate | scriptOfDesignation |
P193693
|
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: [E6, scriptOfDesignation, Latin alphabet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scriptOfDesignation Context triple: [E6, scriptOfDesignation, Latin alphabet]
-
A.
exampleDesignation
Indicates that one entity is identified or labeled as a representative or illustrative instance of another entity.
-
B.
editorialDesignation
Indicates that an entity has been assigned a specific editorial label or status within a publication or editorial workflow.
-
C.
mountDesignation
Indicates that one entity is designated or assigned as the mount (e.g., riding or support animal/vehicle) for another entity.
-
D.
policyDesignation
Indicates that an entity is assigned or labeled with a specific policy or policy classification.
-
E.
bdDesignation
Indicates that one entity is formally assigned or designated as having a particular role, status, or classification in relation to another entity.
- 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_69f76ee0e32c8190b40a3b4cf590337c |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd4f39b5008190b83b3227ce22c509 |
completed | May 8, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_69fd4df17c548190a4e2a6fea70f7e10 |
completed | May 8, 2026, 2:44 a.m. |
| PDg | Predicate description generation | batch_69fd4f38728c8190b3271abc80882cfb |
completed | May 8, 2026, 2:49 a.m. |
Created at: May 3, 2026, 4:19 p.m.