Triple
T10341634
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schengen acquis |
E243139
|
entity |
| Predicate | dateIncorporatedIntoEU |
P93784
|
FINISHED |
| Object | 1999 |
—
|
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: 1999 | Statement: [Schengen acquis, dateIncorporatedIntoEU, 1999]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateIncorporatedIntoEU Context triple: [Schengen acquis, dateIncorporatedIntoEU, 1999]
-
A.
EUMemberSince
Indicates the point in time from which an entity has been a member of the European Union.
-
B.
hasEuropeanUnionMembershipThrough
Indicates that an entity holds membership in the European Union indirectly or by virtue of another entity (such as a state, territory, or organization) through which that membership is conferred.
-
C.
monetaryUnionJoinDate
Indicates the date on which an entity formally joined a specific monetary union.
-
D.
unificationDate
Indicates the date on which two or more previously separate entities were formally unified into a single entity.
-
E.
becameFormalEUInstitutionIn
Indicates that an entity officially acquired the status of a formal institution of the European Union in a specified year or at a specified time.
- 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_69d381af787481908bc401325c760a88 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e91fdb2081909866c6ecf417d75a |
completed | April 7, 2026, 11:23 a.m. |
| PD | Predicate disambiguation | batch_69d4df9dc3208190bf1bd106f44f6202 |
completed | April 7, 2026, 10:42 a.m. |
| PDg | Predicate description generation | batch_69d4e91ce2008190af252c140370b7f2 |
completed | April 7, 2026, 11:23 a.m. |
Created at: April 6, 2026, 11:55 a.m.