Triple
T9298035
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | YF-12C |
E223688
|
entity |
| Predicate | classifiedCoverDesignation |
P87498
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [YF-12C, classifiedCoverDesignation, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: classifiedCoverDesignation Context triple: [YF-12C, classifiedCoverDesignation, yes]
-
A.
protectedDesignation
Indicates that one entity has an officially recognized and legally protected designation or status in relation 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.
exampleDesignation
Indicates that one entity is identified or labeled as a representative or illustrative instance of another entity.
-
D.
associatedDesignation
Indicates that one entity is linked to or identified by a particular designation, title, or label connected with it.
-
E.
classified
Indicates that one entity has assigned another entity to a specific category, group, or type based on defined criteria.
- 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_69ca8423edb08190bc0c91287a484768 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd089e3ae88190aa4181cdd85a67b8 |
completed | April 1, 2026, 11:59 a.m. |
| PD | Predicate disambiguation | batch_69cc7a5aeb748190afb89c6bbd2a6d6f |
completed | April 1, 2026, 1:52 a.m. |
| PDg | Predicate description generation | batch_69cc94b796788190816b71b1e9996288 |
completed | April 1, 2026, 3:44 a.m. |
Created at: March 30, 2026, 7:36 p.m.