Triple
T2141526
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bruttians |
E46769
|
entity |
| Predicate | subjugationCentury |
P10303
|
FINISHED |
| Object | 3rd century BC |
—
|
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: 3rd century BC | Statement: [Bruttians, subjugationCentury, 3rd century BC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subjugationCentury Context triple: [Bruttians, subjugationCentury, 3rd century BC]
-
A.
conqueredIn
Indicates that one entity gained control over another entity or territory as a result of a specific conquest event or campaign.
-
B.
supersededInCentury
Indicates that one entity has been replaced or rendered obsolete by another during a specified century.
-
C.
afterConquestBy
Indicates that one entity exists in a state, condition, or situation that occurs subsequent to and as a result of being conquered by another entity.
-
D.
conquestPeriod
Indicates the time span during which one entity successfully subjugates or takes control of another through conquest.
-
E.
century
chosen
Indicates that an entity is associated with, occurs in, or belongs to a particular 100-year time period.
- 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_69a88a174ab48190a5db20c132e5dccf |
completed | March 4, 2026, 7:37 p.m. |
| NER | Named-entity recognition | batch_69abbf74147c81908793c3694894f94a |
completed | March 7, 2026, 6:02 a.m. |
| PD | Predicate disambiguation | batch_69abbd96a3b0819081efbfef975e1513 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:44 p.m.