Triple
T29044421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bar to the Military Cross |
E738091
|
entity |
| Predicate | isAddedTo |
P4097
|
FINISHED |
| Object | ribbon of the Military Cross |
—
|
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: ribbon of the Military Cross | Statement: [Bar to the Military Cross, isAddedTo, ribbon of the Military Cross]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAddedTo Context triple: [Bar to the Military Cross, isAddedTo, ribbon of the Military Cross]
-
A.
addedTo
chosen
Indicates that one entity has been included or incorporated into another entity, typically as a new component, member, or element.
-
B.
canBeAddedTo
Indicates that one entity is capable of being combined or incorporated with another entity, typically without conflict or incompatibility.
-
C.
addedFor
Indicates that one entity was created, included, or introduced specifically for the benefit, use, or purpose of another entity.
-
D.
hasPutIn
Indicates that one entity has placed or inserted another entity into a container, location, or context.
-
E.
isAComponentOf
Indicates that one entity functions as a constituent part or sub-unit of another, larger 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_69f077efb3848190b41574e1670f6ae2 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f6605fcf7c8190b387ad7b65c9f025 |
completed | May 2, 2026, 8:36 p.m. |
| PD | Predicate disambiguation | batch_69f659d297cc8190b2b962ba30a1edb3 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 10:03 a.m.