Triple
T15229372
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lochnagar Crater |
E363957
|
entity |
| Predicate | preservedSinceApprox |
P29675
|
FINISHED |
| Object | 1970s |
—
|
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: 1970s | Statement: [Lochnagar Crater, preservedSinceApprox, 1970s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: preservedSinceApprox Context triple: [Lochnagar Crater, preservedSinceApprox, 1970s]
-
A.
preservedAt
Indicates that something is kept, maintained, or conserved in a particular place or context.
-
B.
observedSince
Indicates that one entity has been continuously or repeatedly observed starting from a specified point in time.
-
C.
preservesAsTimeOf
Indicates that one entity maintains or records another entity specifically as a temporal reference or time-related designation.
-
D.
betterPreservedThan
Indicates that one entity is in a superior state of preservation or condition compared to another entity.
-
E.
existsSince
chosen
Indicates that an entity has been in existence or valid from a specified point in time onward.
- 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_69d85a0ce24c81909c4d3b6475548c95 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0078ccdf48190b34eabd9e24e45a1 |
completed | April 15, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69deca899d5c8190be4a7c71e1683c69 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:12 a.m.