Triple
T37772764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | de Guise |
E941595
|
entity |
| Predicate | heldTerritorialBaseIn |
P102321
|
FINISHED |
| Object | Duchy of Guise |
—
|
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: Duchy of Guise | Statement: [de Guise, heldTerritorialBaseIn, Duchy of Guise]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heldTerritorialBaseIn Context triple: [de Guise, heldTerritorialBaseIn, Duchy of Guise]
-
A.
heldTerritory
Indicates that one entity maintained control or possession over a specific territory or geographic area.
-
B.
servesAsTerritorialBaseFor
chosen
Indicates that a place or area functions as the primary territorial base or stronghold from which an entity operates or exerts influence.
-
C.
strongholdOf
Indicates that a location serves as a primary fortified base, center of power, or main stronghold for a particular entity.
-
D.
headquartersTerritory
Indicates the territory or region in which an entity’s main headquarters is located.
-
E.
hasTerritorialPossession
Indicates that one entity holds ownership, control, or legal rights over a specific territory or geographic area.
- 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_69f76ee4431881908f87e8892a9f39f3 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbaf1f648c8190b625f91679b6f2ee |
completed | May 6, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69fbadf632ec8190b14991c971258307 |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:19 p.m.