Triple
T5473719
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Victoria Cross for Canada |
E122896
|
entity |
| Predicate | scopeOfActs |
P25607
|
FINISHED |
| Object | in the presence of the enemy |
—
|
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: in the presence of the enemy | Statement: [Victoria Cross for Canada, scopeOfActs, in the presence of the enemy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scopeOfActs Context triple: [Victoria Cross for Canada, scopeOfActs, in the presence of the enemy]
-
A.
scopeOfUse
Indicates the range, context, or conditions under which something is intended, allowed, or applicable to be used.
-
B.
legalScope
Indicates the range, boundaries, or extent of authority, applicability, or effect that something has under a particular legal framework or rule.
-
C.
scopeOfMinistry
Indicates the range of responsibilities, activities, or areas of authority covered by a particular ministry or ministerial role.
-
D.
areaOfLegislation
Indicates that one entity defines, concerns, or governs the legal domain or subject matter covered by another entity.
-
E.
scopeType
chosen
Indicates the specific range, level, or context within which a given relationship, rule, or action is defined or applies.
- 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_69bd46459ff48190823377457bcf7128 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd9230d6d88190a9ac48a4488e1754 |
completed | March 20, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69bd91a58c448190904964a439045e05 |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:09 p.m.