Triple
T15388488
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Firozkoh |
E367974
|
entity |
| Predicate | pointInTimeOfDestruction |
P68493
|
FINISHED |
| Object | early 13th century |
—
|
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: early 13th century | Statement: [Firozkoh, pointInTimeOfDestruction, early 13th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pointInTimeOfDestruction Context triple: [Firozkoh, pointInTimeOfDestruction, early 13th century]
-
A.
timeOfDestruction
chosen
Indicates the specific time at which an entity is destroyed or ceases to exist.
-
B.
dateDestroyed
Indicates the specific date on which an entity was destroyed or ceased to exist.
-
C.
locationOfDestruction
Indicates the place where a destruction event occurred or where something was destroyed.
-
D.
timePeriodOfMajorDestruction
Indicates the time span during which a major destructive event affecting the subject occurred.
-
E.
destroyedDuring
Indicates that one entity was destroyed in the course of, or as a consequence of, a specified event or time period.
- 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_69d85a1551a08190ba2caea7cd51c639 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e761b688190893a81246b735b76 |
completed | April 16, 2026, 1:42 a.m. |
| PD | Predicate disambiguation | batch_69ded27742a881909cd73cc5c7d062fd |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:19 a.m.