Triple
T10135283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Zone of Tangier |
E226838
|
entity |
| Predicate | reintegratedDate |
P53922
|
FINISHED |
| Object | 1956 |
—
|
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: 1956 | Statement: [International Zone of Tangier, reintegratedDate, 1956]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reintegratedDate Context triple: [International Zone of Tangier, reintegratedDate, 1956]
-
A.
reintegratedInto
Indicates that an entity has been brought back and incorporated again into a group, system, or context it was previously separated from.
-
B.
reentryDate
chosen
Indicates the date on which an entity returns or is admitted again after a prior departure, exit, or release.
-
C.
incorporatedIntoOnDate
Indicates that one entity was formally incorporated into or merged with another entity on a specific date.
-
D.
reconstructionEndDate
Indicates the date on which a reconstruction process or project is completed.
-
E.
integratedDate
Indicates the date on which one entity was incorporated, combined, or brought into a larger system or whole.
- 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_69ca8433ec308190b8b25a6fe359c34c |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cde87e1f908190a53865420f2b8f93 |
completed | April 2, 2026, 3:54 a.m. |
| PD | Predicate disambiguation | batch_69cd4ba4f5d88190ba68e63be10b08c7 |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:06 p.m.