Triple
T32696824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I Corps (Grande Armée) |
E836030
|
entity |
| Predicate | usedCorpsNumberingSystem |
P37542
|
FINISHED |
| Object | I |
—
|
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: I | Statement: [I Corps (Grande Armée), usedCorpsNumberingSystem, I]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedCorpsNumberingSystem Context triple: [I Corps (Grande Armée), usedCorpsNumberingSystem, I]
-
A.
corpsNumber
chosen
Indicates that an entity is assigned a specific corps identification number within an organized group or military structure.
-
B.
usesHarmonizedNumberingWith
Indicates that two entities apply the same standardized numbering scheme so their identifiers or codes are directly comparable or aligned.
-
C.
usedHullNumberSystem
Indicates that an entity employed a hull numbering system to identify or classify ships or vessels.
-
D.
hasCabinetNumberingSystem
Indicates that there is a specific scheme or method used to assign and organize identification numbers to cabinets.
-
E.
isNumberedBy
Indicates that an entity is assigned, identified, or organized by a specific number or numbering scheme.
- 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_69f3493323288190a4e88251035fe96e |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6cd126fcc8190aa1f1f146e45ec0c |
completed | May 3, 2026, 4:20 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1470808190b70cdfd7a6395670 |
completed | May 3, 2026, 4:16 a.m. |
Created at: May 1, 2026, 1:10 a.m.