Triple
T21844413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khwadāy-Nāmag |
E539337
|
entity |
| Predicate | approximateCompletionBefore |
P53319
|
FINISHED |
| Object | 7th century CE |
—
|
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 CE | Statement: [Khwadāy-Nāmag, approximateCompletionBefore, 7th century CE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateCompletionBefore Context triple: [Khwadāy-Nāmag, approximateCompletionBefore, 7th century CE]
-
A.
completedBefore
Indicates that one event or action was fully completed prior to the start or completion of another specified event or action.
-
B.
approximateCompletionEra
chosen
Indicates the general historical period or time range during which something was completed, without specifying an exact date.
-
C.
completionOf
Indicates that one entity represents the finished state, fulfillment, or successful conclusion of another entity, process, or requirement.
-
D.
hasApproximateEnd
Indicates that an entity’s end point, time, or boundary is known only approximately rather than precisely.
-
E.
mayBeCompleted
Indicates that an action, process, or task has the potential to be completed, but its completion is not guaranteed.
- 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_69e0c476c3c88190a92d08ebb59a128a |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f0bd5248f08190ba208512eafbe7ad |
completed | April 28, 2026, 1:59 p.m. |
| PD | Predicate disambiguation | batch_69e6be8c14748190bdcc44a14d50bea4 |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 6:55 p.m.