Triple
T17483553
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Government House, Jerusalem |
E425721
|
entity |
| Predicate | UNTSOEstablished |
P127633
|
FINISHED |
| Object | 1948 |
—
|
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: 1948 | Statement: [Government House, Jerusalem, UNTSOEstablished, 1948]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: UNTSOEstablished Context triple: [Government House, Jerusalem, UNTSOEstablished, 1948]
-
A.
dateOfUNTrusteeshipAgreement
Indicates the date on which a United Nations trusteeship agreement was formally established or came into effect between the involved parties.
-
B.
headquartersLocationEstablishedByTreaty
Indicates that an entity’s headquarters location was determined or established as a result of a formal treaty or international agreement.
-
C.
UNMission
Indicates that an entity is a United Nations peacekeeping or political mission operating in a specific area or context.
-
D.
establishedAsCantonmentBy
Indicates that an entity was designated or set up as a cantonment by a specified agent or authority.
-
E.
hasPeacekeepingForcesFrom
Indicates that an entity hosts or is supported by peacekeeping forces that originate from another specified entity.
- 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_69d889dccf7481909264a1844a2e9100 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e451d06c2881909632845dd7a6b1e3 |
completed | April 19, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f341c88190adabe526d8903b05 |
completed | April 18, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69e3bbb37d148190b7f38599c06594ee |
completed | April 18, 2026, 5:13 p.m. |
Created at: April 10, 2026, 5:48 a.m.