Triple
T35849804
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | יהודה ושומרון |
E1036316
|
entity |
| Predicate | previousAdmin |
P12937
|
FINISHED |
| Object | ממלכת ירדן (1948–1967) |
—
|
NE NERFINISHED |
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–1967) | Statement: [יהודה ושומרון, previousAdmin, ממלכת ירדן (1948–1967)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousAdmin Context triple: [יהודה ושומרון, previousAdmin, ממלכת ירדן (1948–1967)]
-
A.
previousAdministrator
chosen
Indicates that one entity formerly held an administrative role or position over another entity before the current administrator.
-
B.
formerAdministeredBy
Indicates that an entity was previously administered or managed by another entity, but is no longer under that administration.
-
C.
previousMaintainer
Indicates that one entity formerly held responsibility for maintaining another entity before the current maintainer.
-
D.
predecessorUser
Indicates that one user previously held a role, position, or state that is now held by another user, making the first user the predecessor of the second.
-
E.
formerAccess
Indicates that an entity previously had access to another entity or resource but no longer does.
- 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_69f76e1b4aa481909630373171eb5ec6 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ff7ae5d088819089aa3b6360b6b749 |
completed | May 9, 2026, 6:20 p.m. |
| PD | Predicate disambiguation | batch_69ff7a4df6488190bf60d675b36b1d6d |
completed | May 9, 2026, 6:17 p.m. |
Created at: May 3, 2026, 4:06 p.m.