Triple
T6119066
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Colonsay House Gardens |
E136434
|
entity |
| Predicate | hasNotableSeason |
P7547
|
FINISHED |
| Object | spring |
—
|
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: spring | Statement: [Colonsay House Gardens, hasNotableSeason, spring]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableSeason Context triple: [Colonsay House Gardens, hasNotableSeason, spring]
-
A.
notableSeason
chosen
Indicates that a particular season is especially significant or noteworthy in relation to an entity (such as a person, team, or series).
-
B.
hasNotableTeamSuccess
Indicates that an entity has achieved significant or distinguished success as part of a team.
-
C.
hasNotablePerformanceIn
Indicates that an entity delivered a significant or distinguished performance within a specified work, event, or context.
-
D.
hasNotablePlayer
Indicates that an entity (such as a team or club) is associated with a player who is particularly distinguished, famous, or significant in its context.
-
E.
hasNotablePerformance
Indicates that an entity has delivered a performance that is distinguished, remarkable, or otherwise noteworthy in a particular context.
- 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_69c0089f851c81909e5e189a617dcff6 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c05bee12488190ab217e8956f2f1f3 |
completed | March 22, 2026, 9:15 p.m. |
| PD | Predicate disambiguation | batch_69c049f9ab3c81909c8ab6466f6a2935 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:14 p.m.