Triple
T34939371
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MORH |
E1007671
|
entity |
| Predicate | usesAcronymFrom |
P148953
|
FINISHED |
| Object | Ministarstvo obrane Republike Hrvatske |
—
|
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: Ministarstvo obrane Republike Hrvatske | Statement: [MORH, usesAcronymFrom, Ministarstvo obrane Republike Hrvatske]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesAcronymFrom Context triple: [MORH, usesAcronymFrom, Ministarstvo obrane Republike Hrvatske]
-
A.
usesAbbreviationOf
chosen
Indicates that one entity employs a shortened or abbreviated form of the name or designation of another entity.
-
B.
hasAcronymOrigin
Indicates that an acronym is derived from or originates from a specific longer expression or name.
-
C.
hasCommonAcronymUsage
Indicates that two terms share the same commonly used acronym in practice.
-
D.
usesAbbreviationIn
Indicates that an entity is referred to by an abbreviated form within a specified context, source, or representation.
-
E.
acronymContext
Indicates that one term is used as an acronym specifically within the contextual scope defined by another entity (such as a document, domain, or usage setting).
- 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_69f76dc513fc819084a1ff52abbfa5bc |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7979a073881909a4fde2558e6b6f3 |
completed | May 3, 2026, 6:44 p.m. |
| PD | Predicate disambiguation | batch_69f7961550f88190b7bb8a9155458b54 |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4 p.m.