Triple
T8473736
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nervii |
E200339
|
entity |
| Predicate | postConquestStatus |
P17908
|
FINISHED |
| Object | subject people of the Roman Empire |
—
|
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: subject people of the Roman Empire | Statement: [Nervii, postConquestStatus, subject people of the Roman Empire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postConquestStatus Context triple: [Nervii, postConquestStatus, subject people of the Roman Empire]
-
A.
postConquestUse
Indicates how something is used, occupied, or functionally repurposed after a conquest has taken place.
-
B.
afterConquest
Indicates that one event, state, or condition occurs subsequent to and as a result of a conquest having taken place.
-
C.
postConflictStatus
chosen
Indicates the condition or circumstances of an entity after a conflict or dispute has concluded.
-
D.
conquestEvent
Indicates an event in which one party gains control over another entity or territory through force or domination.
-
E.
attemptedConquest
Indicates that one entity tried, but did not necessarily succeed, to conquer, subjugate, or take control 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_69ca831a4f348190bfdd09250e86ae35 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe4f7328481909ad19bcf8d182022 |
completed | March 31, 2026, 3:15 p.m. |
| PD | Predicate disambiguation | batch_69cbd104250c8190b4c499dcc9937494 |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:11 p.m.