Triple
T23435683
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stonehenge tunnel |
E563452
|
entity |
| Predicate | designConsideration |
P75654
|
FINISHED |
| Object | protection of archaeological landscape |
—
|
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: protection of archaeological landscape | Statement: [Stonehenge tunnel, designConsideration, protection of archaeological landscape]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designConsideration Context triple: [Stonehenge tunnel, designConsideration, protection of archaeological landscape]
-
A.
hasDesignConsideration
chosen
Indicates that one entity takes another entity into account as a factor, constraint, or requirement in its design or planning.
-
B.
designAspect
Indicates that one entity represents a particular design-related feature, characteristic, or consideration of another entity.
-
C.
designCriteria
Indicates the standards, requirements, or constraints that guide how something should be planned, structured, or created.
-
D.
designUse
Indicates that one entity is used as a design basis, purpose, or intended functional use for another entity.
-
E.
designCheck
Indicates that an entity performs a review or verification of a design to ensure it meets specified requirements or standards.
- 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_69e24553980c8190bb66a2ae0bdab125 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f1a5dbdf248190a09e971f2718d01f |
completed | April 29, 2026, 6:31 a.m. |
| PD | Predicate disambiguation | batch_69f061f92da081908e7f1d0cd1e9b01c |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 5:50 p.m.