Triple
T37639299
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Three Bishoprics |
E936570
|
entity |
| Predicate | recognizedAsFrenchBy |
P195430
|
FINISHED |
| Object | Peace of Westphalia |
—
|
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: Peace of Westphalia | Statement: [Three Bishoprics, recognizedAsFrenchBy, Peace of Westphalia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recognizedAsFrenchBy Context triple: [Three Bishoprics, recognizedAsFrenchBy, Peace of Westphalia]
-
A.
isFrancophoneCounterpartOf
Indicates that one entity serves as the French-speaking or French-language equivalent or counterpart of another entity.
-
B.
usesPrimaryFrenchGateway
Indicates that an entity routes its primary communications or connections through a main gateway located in or associated with French infrastructure or networks.
-
C.
handlesFrenchReleaseOf
Indicates that one entity is responsible for managing or overseeing the French release of another entity.
-
D.
nameInFrench
Indicates that an entity is known or referred to by a specific name expressed in the French language.
-
E.
containsFrenchPhrases
Indicates that the subject includes one or more phrases expressed in the French language.
- 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_69f76ed31d8881908405da6c6d2f0463 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fdd07a34c08190982b8c61c2775cf6 |
completed | May 8, 2026, noon |
| PD | Predicate disambiguation | batch_69fdbd25c7908190b72fca8de7ce503f |
completed | May 8, 2026, 10:38 a.m. |
| PDg | Predicate description generation | batch_69fdd07724f88190a33ec602642d2ea3 |
completed | May 8, 2026, noon |
Created at: May 3, 2026, 4:18 p.m.