Triple
T32480265
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Istaevones |
E830087
|
entity |
| Predicate | traditionalDivisionWith |
P197910
|
FINISHED |
| Object | Ingaevones |
—
|
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: Ingaevones | Statement: [Istaevones, traditionalDivisionWith, Ingaevones]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalDivisionWith Context triple: [Istaevones, traditionalDivisionWith, Ingaevones]
-
A.
traditionalDivisionStatus
Indicates the status or condition of a relationship or grouping as defined by traditional or customary divisions.
-
B.
parallelDivision
Indicates that one entity is divided or partitioned in a way that runs parallel to the division or partitioning of another entity.
-
C.
divisionAbove
Indicates that one entity is positioned in a higher or superior division, tier, or level relative to another entity.
-
D.
modernDivision
Indicates that one entity is a contemporary or currently recognized administrative or organizational subdivision of another entity.
-
E.
divisionContext
Indicates the situational or conceptual setting in which a division operation or separation between entities takes place.
- 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_69f3491ff3b48190b50a7fa00bb05b1f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69feb8e856d48190aa34ad8ee8376e1c |
completed | May 9, 2026, 4:32 a.m. |
| PD | Predicate disambiguation | batch_69feb82a2b6c8190a473cc25976897be |
completed | May 9, 2026, 4:29 a.m. |
| PDg | Predicate description generation | batch_69feb8e6ed7881908446745c89c30784 |
completed | May 9, 2026, 4:32 a.m. |
Created at: May 1, 2026, 12:58 a.m.