Triple
T22660545
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | مقبرة العود |
E559648
|
entity |
| Predicate | تاريخية |
P43343
|
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.
historical
chosen
Indicates that the subject has existed, occurred, or been relevant in the past rather than in the present or future.
-
B.
historicalCategory
Indicates that an entity is classified within a particular historical grouping, period, or type based on its time-related characteristics or context.
-
C.
historicFor
Indicates that something holds historical significance or importance specifically in relation to another entity.
-
D.
politicalHistory
Indicates that there exists a historical political relationship, involvement, or background connecting the entities, such as past offices held, affiliations, or political events linking them.
-
E.
historicalSee
Indicates that one entity observed, encountered, or took visual notice of another entity in the past.
- 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_69e2454a158c819093b8e35f5045efb6 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1765edf88819086c28525e3c73758 |
completed | April 29, 2026, 3:09 a.m. |
| PD | Predicate disambiguation | batch_69ee6294c4c08190b7e4829f4b9af24b |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:07 p.m.