Triple
T2829843
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Belgium |
E62208
|
entity |
| Predicate | joinedBelgiumFrom |
P42728
|
FINISHED |
| Object | Germany after World War I |
—
|
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: Germany after World War I | Statement: [East Belgium, joinedBelgiumFrom, Germany after World War I]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: joinedBelgiumFrom Context triple: [East Belgium, joinedBelgiumFrom, Germany after World War I]
-
A.
unificationDate
Indicates the date on which two or more previously separate entities were formally unified into a single entity.
-
B.
EUMemberSince
Indicates the point in time from which an entity has been a member of the European Union.
-
C.
countryJoined
Indicates that a country became a member of, or formally entered into, a specific organization, union, alliance, or agreement.
-
D.
otherRegionsOfBelgium
Indicates that the related entities are regions of Belgium that are distinct from a specified primary Belgian region.
-
E.
integratedIntoFrenchCrown
Indicates that a territory, institution, or authority was formally absorbed into and brought under the direct control of the French royal state.
- 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_69ab4c3c39188190955b9c49d98463d8 |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abdebbde4881908dfa78e28c7018e0 |
completed | March 7, 2026, 8:15 a.m. |
| PD | Predicate disambiguation | batch_69abdd0acab881909e8c25cbef83678c |
completed | March 7, 2026, 8:08 a.m. |
| PDg | Predicate description generation | batch_69abddccd50c8190a975942f46cfc01f |
completed | March 7, 2026, 8:11 a.m. |
Created at: March 6, 2026, 10:01 p.m.