Triple
T34534406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Usher Gardens |
E886626
|
entity |
| Predicate | developedInStyleOf |
P53448
|
FINISHED |
| Object | William Robinson |
—
|
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: William Robinson | Statement: [Mount Usher Gardens, developedInStyleOf, William Robinson]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developedInStyleOf Context triple: [Mount Usher Gardens, developedInStyleOf, William Robinson]
-
A.
wasDevelopedIn
Indicates that an entity (such as a product, technology, or work) came into existence or was created during a specific time period or at a particular place.
-
B.
developedAs
Indicates that one entity was created, designed, or evolved specifically to function as or replace another entity.
-
C.
developmentStyle
chosen
Indicates the manner or approach in which something is developed, such as the methodology, process, or style guiding its creation or evolution.
-
D.
developedWithin
Indicates that something was created, produced, or brought into existence inside a specified context, boundary, or time frame.
-
E.
developedWith
Indicates that something was created, built, or produced using a specified tool, technology, method, or collaborator.
- 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_69f349ce5eb881909e431c670944aa68 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd231cab588190ad0953dc8f4af8f2 |
completed | May 7, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69fd1aa3f1c481909fe6e9cab1383551 |
completed | May 7, 2026, 11:05 p.m. |
Created at: May 1, 2026, 2:02 a.m.