Triple
T29129537
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Germania Superior |
E738331
|
entity |
| Predicate | territoryLaterControlledBy |
P169301
|
FINISHED |
| Object | Alamanni |
—
|
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: Alamanni | Statement: [Germania Superior, territoryLaterControlledBy, Alamanni]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: territoryLaterControlledBy Context triple: [Germania Superior, territoryLaterControlledBy, Alamanni]
-
A.
conqueredInPartBy
Indicates that one entity has gained control over a portion, but not the entirety, of another entity through conquest.
-
B.
wasCoreTerritoryOf
Indicates that a region historically formed the central or most important territorial area belonging to a particular political or cultural entity.
-
C.
kingdomAnnexedBy
Indicates that a kingdom has been taken over and incorporated into another political entity through annexation.
-
D.
lastPoliticalControl
Indicates which political entity most recently held governing authority or control over another entity or territory.
-
E.
lastTerritoriesConqueredBy
Indicates that the referenced territories are the most recent ones taken control of through conquest by a specified entity.
- 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_69f07cb29cdc8190afa55444553de60c |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f67de7792c81909b5e4e812d143624 |
completed | May 2, 2026, 10:42 p.m. |
| PD | Predicate disambiguation | batch_69f678ce54b081908c26edfd49e39c60 |
completed | May 2, 2026, 10:21 p.m. |
| PDg | Predicate description generation | batch_69f67d31cc60819084f64bd056e1ea4d |
completed | May 2, 2026, 10:39 p.m. |
Created at: April 28, 2026, 11:30 a.m.