Triple
T28846344
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Legio VI Victrix |
E728464
|
entity |
| Predicate | hasNumeralComponent |
P191087
|
FINISHED |
| Object | VI |
—
|
NE NERFINISHED |
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: VI | Statement: [Legio VI Victrix, hasNumeralComponent, VI]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNumeralComponent Context triple: [Legio VI Victrix, hasNumeralComponent, VI]
-
A.
hasNumeral
Indicates that one entity is associated with a numeral representation or numeric symbol of another entity.
-
B.
hasUseInNumerals
Indicates that something is employed or functions as a component within numeral systems or numerical representations.
-
C.
hasArabicNumeral
Indicates that an entity is associated with, represented by, or expressed using an Arabic numeral.
-
D.
hasNumericalValue
Indicates that an entity is associated with a specific numeric quantity or measurement.
-
E.
containsNumber
Indicates that one entity includes or has at least one numeric value or digit within it.
- F. None of above. chosen
Provenance (4 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_69f0319e8e7c8190b37288c8845b9dbc |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69fcda3699948190adb57625bae08091 |
completed | May 7, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fd16d08190b0aca6e19a632e99 |
completed | May 7, 2026, 6:25 p.m. |
| PDg | Predicate description generation | batch_69fcda35dc048190a3c90e15230900e0 |
completed | May 7, 2026, 6:30 p.m. |
Created at: April 28, 2026, 6:42 a.m.