Triple
T992826
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holy Land |
E21427
|
entity |
| Predicate | historicalControlBy |
P5058
|
FINISHED |
| Object | Ancient Israelite kingdoms |
—
|
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: Ancient Israelite kingdoms | Statement: [Holy Land, historicalControlBy, Ancient Israelite kingdoms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalControlBy Context triple: [Holy Land, historicalControlBy, Ancient Israelite kingdoms]
-
A.
historicallyControlledBy
chosen
Indicates that an entity was under the control, rule, or governance of another entity during some period in the past.
-
B.
historicalMethod
Indicates that a particular method, approach, or technique was used in the past, typically in a historical context or during a previous period of activity.
-
C.
historicalState
Indicates that an entity existed in a particular state or condition during a specified time in the past.
-
D.
historicalFunction
Indicates the role, purpose, or activity an entity had during a past period or in a historical context.
-
E.
historicalForm
Indicates that one entity is an earlier or historically attested form or variant of 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_69a493c476b48190b41fc5e793171cc6 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b4c3f7b48190a31308bdc09817c6 |
completed | March 1, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69a4b2adbde48190b07966d0c3179516 |
completed | March 1, 2026, 9:42 p.m. |
Created at: March 1, 2026, 7:41 p.m.