Triple
T14040821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | E85 |
E337838
|
entity |
| Predicate | internalDesignation |
P75661
|
FINISHED |
| Object | E85 |
—
|
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: E85 | Statement: [E85, internalDesignation, E85]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: internalDesignation Context triple: [E85, internalDesignation, E85]
-
A.
hasInternalDesignationFor
chosen
Indicates that one entity assigns or uses an internal label, code, or designation to refer to another entity.
-
B.
internationalDesignation
Indicates that an entity has been assigned a formal status, code, or recognition by an international body or under an internationally agreed system.
-
C.
systemDesignation
Indicates that an entity has been assigned a specific formal label or identifier within a defined system or framework.
-
D.
protectedDesignation
Indicates that one entity has an officially recognized and legally protected designation or status in relation to another entity.
-
E.
sideDesignation
Indicates how an entity is classified or labeled with respect to a particular side, position, or alignment within a relationship or context.
- 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_69d81c664e48819088cbd8f433aeffe5 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de311814e48190adb637e1c97c0658 |
completed | April 14, 2026, 12:20 p.m. |
| PD | Predicate disambiguation | batch_69de05ab36b48190920efb1869bdb1fe |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:20 p.m.