Triple
T10629624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Canadian Infantry Corps |
E250416
|
entity |
| Predicate | hasOperationalLevel |
P2393
|
FINISHED |
| Object | tactical |
—
|
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: tactical | Statement: [Royal Canadian Infantry Corps, hasOperationalLevel, tactical]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOperationalLevel Context triple: [Royal Canadian Infantry Corps, hasOperationalLevel, tactical]
-
A.
hasOperationalComponent
Indicates that an entity includes, uses, or depends on another entity as a functional or operational part of its overall system or process.
-
B.
isOperationalRank
Indicates that a given rank or position is recognized as an official operational rank within a hierarchy or organization.
-
C.
hasOperationalSignificance
Indicates that something plays a meaningful, practical role or effect in how a system, process, or operation functions or is carried out.
-
D.
hasLevel
chosen
Indicates that an entity possesses or is associated with a particular degree, rank, or stage within an ordered scale or hierarchy.
-
E.
hasUsageLevel
Indicates the degree or intensity with which something is used or utilized.
- 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_69d6aa5993448190a493b790b8f85010 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6df92f8388190a8bcff96809d8eb4 |
completed | April 8, 2026, 11:06 p.m. |
| PD | Predicate disambiguation | batch_69d6dd7fae088190973f70c69738af49 |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 9 p.m.