Triple
T26795969
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ministry of Defense of the Kingdom of Laos |
E670947
|
entity |
| Predicate | usedShortName |
P99167
|
FINISHED |
| Object | Laotian Ministry of Defense |
—
|
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: Laotian Ministry of Defense | Statement: [Ministry of Defense of the Kingdom of Laos, usedShortName, Laotian Ministry of Defense]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedShortName Context triple: [Ministry of Defense of the Kingdom of Laos, usedShortName, Laotian Ministry of Defense]
-
A.
isShortName
Indicates that one name is an abbreviated or shorter form of another name.
-
B.
commonShortNameFor
chosen
Indicates that one entity is a commonly used short or abbreviated name for another entity.
-
C.
usesAbbreviationIn
Indicates that an entity is referred to by an abbreviated form within a specified context, source, or representation.
-
D.
usesAbbreviationOf
Indicates that one entity employs a shortened or abbreviated form of the name or designation of another entity.
-
E.
bearerShortName
Indicates that an entity serves as the short or abbreviated name used to identify the bearer in the context of a relationship or action.
- 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_69eeb31fbd888190a82dac5822e453bc |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f621fcea1481909b6f8b3af1ee6820 |
completed | May 2, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69f620debeb48190b7db395fb86cf8d9 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 4:19 a.m.