Triple
T26138146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | تماثيل رمسيس الثاني |
E659436
|
entity |
| Predicate | تعود_إلى |
P159988
|
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.
returnsTo
Indicates that an entity goes back to a previous location, state, or entity it was associated with before.
-
B.
returnToRomeTo
Indicates that an entity goes back or returns to the location Rome.
-
C.
returnedToTour
Indicates that an entity resumed or went back to participating in a tour after having left or paused it.
-
D.
returnedFrom
Indicates that an entity has come back or been sent back from a specified source, location, or prior state.
-
E.
forcedToReturnTo
Indicates that one entity is compelled, against its preference or by external pressure or requirement, to go back to a previous place, state, or situation.
- 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_69ee5bc3c20c8190bf2cf272f4170e95 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f60be1d2408190820365bf7d8436bd |
completed | May 2, 2026, 2:36 p.m. |
| PD | Predicate disambiguation | batch_69f5b0021da88190bdd4cf2698c23edf |
completed | May 2, 2026, 8:04 a.m. |
| PDg | Predicate description generation | batch_69f5f6b32a8881909baa0db57b80d56a |
completed | May 2, 2026, 1:05 p.m. |
Created at: April 26, 2026, 8:18 p.m.