Triple
T12998587
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UAE Constitution |
E322107
|
entity |
| Predicate | madePermanentOn |
P59755
|
FINISHED |
| Object | 1996-05-27 |
—
|
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: 1996-05-27 | Statement: [UAE Constitution, madePermanentOn, 1996-05-27]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: madePermanentOn Context triple: [UAE Constitution, madePermanentOn, 1996-05-27]
-
A.
madePermanentBy
Indicates that one entity causes another entity, condition, or status to become lasting, fixed, or indefinitely maintained.
-
B.
permanentAdoption
Indicates a lasting, legally recognized adoption relationship in which the adoptee becomes a permanent member of the adopter’s family.
-
C.
permanence
Indicates that a state, condition, or relationship continues to hold over time without significant change or interruption.
-
D.
madeAt
chosen
Indicates the specific place or time at which something was created, produced, or manufactured.
-
E.
establishedTo
Indicates that one entity was created, founded, or set up for the purpose of serving, supporting, or enabling another 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_69d8076479b8819090afce3591939cdf |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97e7b268c8190b8bb855e9de23c3b |
completed | April 10, 2026, 10:49 p.m. |
| PD | Predicate disambiguation | batch_69d97dc153a081909d13a694993f074a |
completed | April 10, 2026, 10:46 p.m. |
Created at: April 9, 2026, 8:46 p.m.