Triple
T36629539
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | E8 |
E904273
|
entity |
| Predicate | designationScript |
P199776
|
FINISHED |
| Object | Latin alphabet |
—
|
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 alphabet | Statement: [E8, designationScript, Latin alphabet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designationScript Context triple: [E8, designationScript, Latin alphabet]
-
A.
designationComponent
Indicates that one entity functions as a component or constituent part of another entity’s designation or formal naming.
-
B.
designationFor
Indicates that one entity serves as the official title, label, or role name assigned to another entity.
-
C.
designationAct
Indicates an official act by which an authority formally assigns, names, or appoints an entity to a specific role, status, or function.
-
D.
designationType
Indicates the specific category or kind of formal status, title, or label that has been assigned in a designation relationship.
-
E.
designationCategory
Indicates the classification or type of designation assigned to an entity within a broader designation system.
- 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_69f76e6ae750819096911e6e2d4d12c5 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff56ef0a5c8190ae729d66a8cf7fc4 |
completed | May 9, 2026, 3:46 p.m. |
| PD | Predicate disambiguation | batch_69ff539859c481909ec56310da418688 |
completed | May 9, 2026, 3:32 p.m. |
| PDg | Predicate description generation | batch_69ff56edc4d081908f1d263e05cbd512 |
completed | May 9, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:11 p.m.