Triple
T5096484
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scone Palace |
E114876
|
entity |
| Predicate | notablePlanting |
P45448
|
FINISHED |
| Object | ancient trees and pinetum |
—
|
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: ancient trees and pinetum | Statement: [Scone Palace, notablePlanting, ancient trees and pinetum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notablePlanting Context triple: [Scone Palace, notablePlanting, ancient trees and pinetum]
-
A.
notableTreeSpecies
Indicates that the subject place or area is known for, or characterized by, the specified tree species.
-
B.
famousPlants
chosen
Indicates that the plants in question are widely known or celebrated, typically for their distinctive characteristics, history, or cultural significance.
-
C.
hasCommemorativePlanting
Indicates that an entity has a specific plant or planting established to commemorate or honor a person, event, or occasion.
-
D.
involvesPlant
Indicates that the relationship or action includes or pertains to a plant as a participating entity.
-
E.
plantType
Indicates the specific kind or category of plant that an entity is classified as.
- 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_69bd443fc49c819089629c00e311310c |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd75652a8081908386718f1fdb1de3 |
completed | March 20, 2026, 4:27 p.m. |
| PD | Predicate disambiguation | batch_69bd715e06808190931934dc9930f997 |
completed | March 20, 2026, 4:10 p.m. |
Created at: March 20, 2026, 1:40 p.m.