Triple
T24233812
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Léman department |
E601813
|
entity |
| Predicate | annexationOfGeneva |
P151413
|
FINISHED |
| Object | 1798 |
—
|
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: 1798 | Statement: [Léman department, annexationOfGeneva, 1798]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: annexationOfGeneva Context triple: [Léman department, annexationOfGeneva, 1798]
-
A.
annexationBy
chosen
Indicates that one entity has been incorporated into and brought under the control or sovereignty of another entity, typically through formal or forceful territorial expansion.
-
B.
annexationControversy
Indicates a dispute or conflict over the legitimacy, process, or consequences of one entity annexing territory or authority from another.
-
C.
annexationInstrument
Indicates the legal or formal instrument (such as a treaty, decree, or law) by which one entity annexes or incorporates another.
-
D.
GenevaActAdopted
Indicates that a formal act, agreement, or resolution associated with Geneva has been officially adopted or approved.
-
E.
annexationPolicy
Indicates a policy or practice of formally incorporating one territory into the jurisdiction or sovereignty of another.
- 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_69e29538aafc8190a2386fdebbd1393b |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f28a99889c819080efdec76be04646 |
completed | April 29, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69f1c448abec8190b87cbf9ed419a309 |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:02 a.m.