Triple
T2250090
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Order of the Lion of Finland |
E49596
|
entity |
| Predicate | typeOfRecipients |
P379
|
FINISHED |
| Object | civilians |
—
|
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: civilians | Statement: [Order of the Lion of Finland, typeOfRecipients, civilians]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfRecipients Context triple: [Order of the Lion of Finland, typeOfRecipients, civilians]
-
A.
hasTypeOfRecipient
chosen
Indicates that an entity is associated with a specific category or kind of recipient it is intended for or directed to.
-
B.
scopeOfRecipients
Indicates the range or group of recipients to whom something (such as information, communication, or benefits) is directed or applicable.
-
C.
totalRecipients
Indicates the total number of distinct entities that receive something in the context of the described relationship or action.
-
D.
notableRecipientType
Indicates that an entity is notably recognized as a recipient of something (such as an award, honor, or distinction) of a specified type.
-
E.
individualRecipient
Indicates that a specific individual is the direct recipient or beneficiary of something (such as an item, message, 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_69a88aaa9250819095e127d0d77e8a32 |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc11b61888190af3b11b87dc8e0dc |
completed | March 7, 2026, 6:09 a.m. |
| PD | Predicate disambiguation | batch_69abbdb160248190aa75b38f11ad8602 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:47 p.m.