Triple
T29693480
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MSHE RF |
E751274
|
entity |
| Predicate | shortNameEnglish |
P51963
|
FINISHED |
| Object | MSHE RF |
—
|
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: MSHE RF | Statement: [MSHE RF, shortNameEnglish, MSHE RF]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shortNameEnglish Context triple: [MSHE RF, shortNameEnglish, MSHE RF]
-
A.
hasOfficialShortNameInEnglish
chosen
Indicates that an entity has a designated official short form of its name expressed in English.
-
B.
shortFormLanguage
Indicates that one entity is a shortened or abbreviated language representation or code corresponding to another language entity.
-
C.
shortNameInDanish
Indicates that one entity is the short or abbreviated name of another entity when expressed in Danish.
-
D.
shortNameInJapanese
Indicates that an entity has a specific abbreviated or shorter form of its name expressed in the Japanese language.
-
E.
shortDesignation
Indicates that one entity serves as a brief or abbreviated designation (such as a short name, code, or label) for another entity.
- 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_69f0d625b09481909b0b69aea1e846c8 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f672963f0481909795a3384a2d3bb4 |
completed | May 2, 2026, 9:54 p.m. |
| PD | Predicate disambiguation | batch_69f6659f246081909821c5f452d14e8f |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 7:18 p.m.