Triple
T15119054
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | XVI Corps (Union Army) |
E361118
|
entity |
| Predicate | usedRomanNumeralDesignation |
P7465
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [XVI Corps (Union Army), usedRomanNumeralDesignation, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedRomanNumeralDesignation Context triple: [XVI Corps (Union Army), usedRomanNumeralDesignation, true]
-
A.
usesRomanNumerals
Indicates that something represents numbers or sequences using the Roman numeral system rather than standard Arabic digits.
-
B.
RomanNumeral
chosen
Indicates that something is represented or written using the Roman numeral system.
-
C.
roleInRomanSystem
Indicates that one entity holds a specific function, position, or status within the structure or hierarchy of the Roman system.
-
D.
usedInRomanPeriodFor
Indicates that something served a particular function, purpose, or application during the Roman period.
-
E.
usesNumeralsFrom
Indicates that one writing system, notation, or representation employs the numeral symbols originating from another system.
- 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_69d85a0491ec8190830960be8fafb994 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0059e036c8190959ff3bde8f2356f |
completed | April 15, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69deb96c1d9c81909351558ed97bc5b7 |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:06 a.m.