Triple
T13405920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carse of Gowrie |
E319955
|
entity |
| Predicate | hasNotableProduce |
P26032
|
FINISHED |
| Object | Carse of Gowrie apples |
—
|
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: Carse of Gowrie apples | Statement: [Carse of Gowrie, hasNotableProduce, Carse of Gowrie apples]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableProduce Context triple: [Carse of Gowrie, hasNotableProduce, Carse of Gowrie apples]
-
A.
hasProduction
chosen
Indicates that an entity is associated with, or responsible for, the creation or manufacture of another entity or product.
-
B.
doesNotProduce
Indicates that one entity fails to generate, create, or yield another entity or outcome.
-
C.
hasProductionValue
Indicates that something possesses or is associated with a particular level or type of production quality or cost.
-
D.
hasNotableComposition
Indicates that an entity is associated with a specific composition (e.g., musical, artistic, or written work) that is considered notable or significant.
-
E.
hasNotableFeature
Indicates that an entity possesses a specific characteristic, trait, or attribute that is considered significant or noteworthy.
- 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_69d806b943cc8190b6af624d385d7e12 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbae4be498819094798473a1bfd853 |
completed | April 12, 2026, 2:38 p.m. |
| PD | Predicate disambiguation | batch_69d9a0355de48190bb3fb96912e20df3 |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:34 p.m.