Triple
T3344381
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ulpius |
E70334
|
entity |
| Predicate | positionInRomanName |
P1082
|
FINISHED |
| Object | middle name |
—
|
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: middle name | Statement: [Ulpius, positionInRomanName, middle name]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInRomanName Context triple: [Ulpius, positionInRomanName, middle name]
-
A.
positionInRomanCalendar
Indicates the ordinal placement or rank that something occupies within the sequence of months or days in the Roman calendar.
-
B.
hasRomanName
Indicates that an entity is associated with or known by a name derived from or used in ancient Rome.
-
C.
namePosition
chosen
Indicates the positional or ordering relationship of a name within a sequence or structured context (e.g., first, last, or specific index).
-
D.
usesRomanNumerals
Indicates that something represents numbers or sequences using the Roman numeral system rather than standard Arabic digits.
-
E.
nameInRomanian
Indicates that one entity is the Romanian-language name or designation of another entity.
- 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_69ad85a405e48190b6e68de7cf9f319e |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb1f23008819084ea68b8431c50ab |
completed | March 8, 2026, 5:29 p.m. |
| PD | Predicate disambiguation | batch_69ada42df1d48190874bb05f95deefde |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:12 p.m.