Triple
T37943794
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Navy of the Kingdom of Serbia |
E946552
|
entity |
| Predicate | usedUniformOf |
P2930
|
FINISHED |
| Object | Armed Forces of the Kingdom of Serbia |
—
|
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: Armed Forces of the Kingdom of Serbia | Statement: [Navy of the Kingdom of Serbia, usedUniformOf, Armed Forces of the Kingdom of Serbia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedUniformOf Context triple: [Navy of the Kingdom of Serbia, usedUniformOf, Armed Forces of the Kingdom of Serbia]
-
A.
usesUniform
chosen
Indicates that one entity regularly wears or employs a standardized set of clothing or equipment designated as a uniform.
-
B.
usedUniformColor
Indicates that multiple entities share or employed the same uniform color in a given context.
-
C.
isUniform
Indicates that all elements or parts within a given set, structure, or context share the same characteristics or value.
-
D.
areUniform
Indicates that all elements in a given set or collection share the same value, property, or characteristic.
-
E.
usedStyle
Indicates that one entity employed or applied a particular style, method, or manner associated with 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_69f76ef531ac8190ae6d99e5786e76ec |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc7b78f9481909f4f8fc2e3fdcde1 |
completed | May 6, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69fbbd18c9908190928d274f8731dfa8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:20 p.m.