Triple
T31802378
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prüm Abbey |
E811774
|
entity |
| Predicate | ownedTerritoriesIn |
P136567
|
FINISHED |
| Object | Eifel |
—
|
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: Eifel | Statement: [Prüm Abbey, ownedTerritoriesIn, Eifel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ownedTerritoriesIn Context triple: [Prüm Abbey, ownedTerritoriesIn, Eifel]
-
A.
collectiveTerritories
Indicates that multiple entities share or jointly possess a set of territories as a collective whole.
-
B.
representedTerritories
Indicates that one entity serves as the official representative or governing authority for certain territories or geographic areas.
-
C.
outsideTerritoriesGovernedBy
Indicates that one entity is located or occurs beyond the geographic or jurisdictional boundaries controlled or administered by another entity.
-
D.
ownedLandBy
chosen
Indicates that one entity possesses legal or recognized ownership rights over a piece or area of land associated with another entity.
-
E.
mainTerritoryOfInfluence
Indicates the primary geographic area where an entity exerts the most significant control, impact, or influence.
- 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_69f348e70d188190b4637c5509f81274 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca3dedc81908b519d53d2909868 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 30, 2026, 11:42 p.m.