Triple
T15152593
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | William VII of Chalon-Arlay |
E361982
|
entity |
| Predicate | territoryHeld |
P28640
|
FINISHED |
| Object | lands in Franche-Comté |
—
|
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: lands in Franche-Comté | Statement: [William VII of Chalon-Arlay, territoryHeld, lands in Franche-Comté]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: territoryHeld Context triple: [William VII of Chalon-Arlay, territoryHeld, lands in Franche-Comté]
-
A.
heldTerritory
chosen
Indicates that one entity maintained control or possession over a specific territory or geographic area.
-
B.
gainedTerritory
Indicates that one entity has acquired control over additional land or area from another entity or from a neutral state.
-
C.
acquiredTerritoryBy
Indicates a relationship where one entity gains control or ownership of a territory through a specific means, event, or process.
-
D.
acquiredTerritoryFrom
Indicates that one entity gained control or ownership of a territory that previously belonged to another entity.
-
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_69d85a0759908190b8a051d2e2a1cbe6 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e00609040081908c849475a2fa6443 |
completed | April 15, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69deb9779acc81908ed2dad382c42dca |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:07 a.m.