Triple
T4202619
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Benelux Court of Justice |
E86103
|
entity |
| Predicate | dateFormallyEstablished |
P9196
|
FINISHED |
| Object | 1974-01-01 |
—
|
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: 1974-01-01 | Statement: [Benelux Court of Justice, dateFormallyEstablished, 1974-01-01]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateFormallyEstablished Context triple: [Benelux Court of Justice, dateFormallyEstablished, 1974-01-01]
-
A.
eraOfEstablishment
Indicates the time period or historical era during which an entity was founded or established.
-
B.
establishedAt
chosen
Indicates the specific time or date at which something (such as an organization, system, or entity) was founded or brought into existence.
-
C.
isFoundedOn
Indicates that one entity is established, created, or based upon another entity as its foundational source or principle.
-
D.
governingBodyEstablished
Indicates that a particular governing body was formally created or brought into existence for an entity or domain.
-
E.
establishedFrom
Indicates that something was created, founded, or formed starting from a specified source, origin, or prior entity.
- 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_69aed93b89f48190a31f6d57c760e42f |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af037f1de4819088d6bf544317a694 |
completed | March 9, 2026, 5:29 p.m. |
| PD | Predicate disambiguation | batch_69af01959c4881909eb1adcb3bdadbe6 |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:49 p.m.