Triple
T7912529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dhul-Qarnayn |
E183732
|
entity |
| Predicate | timeOfMention |
P1936
|
FINISHED |
| Object | 7th century revelation context |
—
|
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: 7th century revelation context | Statement: [Dhul-Qarnayn, timeOfMention, 7th century revelation context]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeOfMention Context triple: [Dhul-Qarnayn, timeOfMention, 7th century revelation context]
-
A.
timeSincePreviousVisitMentioned
Indicates that the elapsed time since a previous visit is explicitly referenced or specified in the context.
-
B.
timeOfAppearance
Indicates the specific time at which an entity or event becomes visible, present, or first occurs.
-
C.
time
chosen
Indicates a temporal relationship specifying when an event occurs or how entities are ordered or related in time.
-
D.
followsTime
Indicates that one event, state, or time period occurs after and in temporal succession to another.
-
E.
recognizedSince
Indicates that one entity has formally acknowledged, accepted, or identified another entity as valid or legitimate starting from a specific point in time.
- 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_69ca828dec0c81908b8f55a4dbbb53ff |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3a7383cc819084eab19799209d2e |
completed | March 31, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69cae92f9498819085277879e59aa072 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5:04 p.m.