Triple
T25873650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ellisland Farm |
E651827
|
entity |
| Predicate | notableWorkComposedHere |
P20271
|
FINISHED |
| Object | Tam o’ Shanter |
—
|
NE NERFINISHED |
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: Tam o’ Shanter | Statement: [Ellisland Farm, notableWorkComposedHere, Tam o’ Shanter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableWorkComposedHere Context triple: [Ellisland Farm, notableWorkComposedHere, Tam o’ Shanter]
-
A.
notableWorkComposedWith
Indicates that a notable work was created using, in collaboration with, or through the involvement of a particular tool, medium, system, or co-creative entity.
-
B.
notableComposition
Indicates that an entity is a significant or well-known work created by another entity, such as a notable musical, literary, or artistic composition.
-
C.
notableWorkSetHere
Indicates that a notable creative work is set in or takes place within the referenced location.
-
D.
notableWorkWrittenThere
chosen
Indicates that a notable work was written at or in the specified place.
-
E.
notablePlaceOfWork
Indicates that there is a notable or significant place where the entity has worked or been employed.
- 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_69e7ab3ad9d88190841ddcb93ab02e96 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69fdd2be648c8190b60b3d1caeb44364 |
completed | May 8, 2026, 12:10 p.m. |
| PD | Predicate disambiguation | batch_69fdd14a5c708190a6f95ec61f4fc28f |
completed | May 8, 2026, 12:04 p.m. |
Created at: April 22, 2026, 8:12 a.m.