Triple
T2025849
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Armed Forces of Luxembourg |
E44404
|
entity |
| Predicate | sizeCharacteristic |
P28652
|
FINISHED |
| Object | small armed forces |
—
|
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: small armed forces | Statement: [Armed Forces of Luxembourg, sizeCharacteristic, small armed forces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sizeCharacteristic Context triple: [Armed Forces of Luxembourg, sizeCharacteristic, small armed forces]
-
A.
sizeDescription
chosen
Indicates a relationship where one entity provides descriptive information about the size or scale of another entity.
-
B.
sizeDefinedBy
Indicates that the size or magnitude of one entity is determined, constrained, or specified by another entity.
-
C.
bodySize
Indicates the relative physical magnitude or scale of an entity’s body, such as how large or small it is.
-
D.
legCharacteristic
Indicates a characteristic, property, or attribute that specifically pertains to the legs of an entity.
-
E.
sizeIncreasedTo
Indicates that an entity’s size has changed and reached a specified larger value or magnitude.
- 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_69a889144f2481909932f0746a93023d |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb8f3faa08190a48ae1355d6e009f |
completed | March 7, 2026, 5:34 a.m. |
| PD | Predicate disambiguation | batch_69abb7a656248190ac2ced196b35bc6b |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:38 p.m.