Triple
T33791914
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | عهد الدولة الموحدية |
E865953
|
entity |
| Predicate | يقع_زمنياً_ضمن |
P41036
|
FINISHED |
| Object | القرن الثاني عشر الميلادي |
—
|
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: القرن الثاني عشر الميلادي | Statement: [عهد الدولة الموحدية, يقع_زمنياً_ضمن, القرن الثاني عشر الميلادي]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: يقع_زمنياً_ضمن Context triple: [عهد الدولة الموحدية, يقع_زمنياً_ضمن, القرن الثاني عشر الميلادي]
-
A.
locatedInTimeBefore
Indicates that one temporal event or interval occurs entirely before another in time.
-
B.
זמנם
Indicates a relationship involving the time allotted to, belonging to, or associated with certain entities (e.g., “their time”).
-
C.
locatedInHistoricPeriod
chosen
Indicates that an entity exists, occurs, or is situated within a specific historic period or era.
-
D.
existsWithin
Indicates that one entity is located inside the spatial, temporal, or conceptual boundaries of another entity.
-
E.
historicallyCircumscribedBy
Indicates that one entity’s historical existence, development, or significance is bounded, defined, or delimited by the historical context or period associated with 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_69f3498f99f481909cb271f4965a7594 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc59518081908b0275f47721d561 |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:45 a.m.