Triple
T11740800
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mülhausen, Alsace-Lorraine, German Empire |
E279147
|
entity |
| Predicate | isContestedRegion |
P101100
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Mülhausen, Alsace-Lorraine, German Empire, isContestedRegion, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isContestedRegion Context triple: [Mülhausen, Alsace-Lorraine, German Empire, isContestedRegion, true]
-
A.
alsoContestedIn
Indicates that the same issue, claim, or matter is being disputed or challenged in another context, case, or proceeding as well.
-
B.
contestedBy
Indicates that one party challenges, disputes, or opposes a claim, decision, or position held by another party.
-
C.
wasContestedBetween
Indicates that an event, position, or resource was the subject of competition or dispute involving two or more opposing parties.
-
D.
controlContested
Indicates that authority or dominance over something is disputed or challenged between two or more parties.
-
E.
countryContestedBy
Indicates that control, ownership, or sovereignty over a country is disputed by multiple parties or entities.
- 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_69d6aaffec6881908bead509e8621742 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a4f025f88190a39280806c9d7c33 |
completed | April 10, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69d88a813cc48190a3dfdc60e8af80ae |
completed | April 10, 2026, 5:28 a.m. |
| PDg | Predicate description generation | batch_69d890458d948190b15054c9ba0fd923 |
completed | April 10, 2026, 5:53 a.m. |
Created at: April 8, 2026, 9:41 p.m.