Triple
T27667125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Stifle Tower |
E697255
|
entity |
| Predicate | associatedAreaOnCourt |
P202030
|
FINISHED |
| Object | paint |
—
|
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: paint | Statement: [The Stifle Tower, associatedAreaOnCourt, paint]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedAreaOnCourt Context triple: [The Stifle Tower, associatedAreaOnCourt, paint]
-
A.
primaryLocationOnCourt
Indicates the main area or position on the court where an entity is typically located or operates.
-
B.
positionInCourt
Indicates the specific role or standing an entity holds within a court setting or judicial proceeding.
-
C.
hasCourtSurface
Indicates that something (such as a court or playing area) possesses a specific type of surface.
-
D.
centreCourtName
Indicates the name assigned to the central court associated with a particular venue or event.
-
E.
positionInTennis
Indicates the specific role or court location a player occupies during a tennis match or point.
- F. None of above. chosen
Provenance (4 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_69ef590b85a4819083ec7c12bd3c9c10 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_6a0048697bd081909073640666ca6a96 |
completed | May 10, 2026, 8:57 a.m. |
| PD | Predicate disambiguation | batch_6a0047bf3c248190a9ac97a7afdfe2cb |
completed | May 10, 2026, 8:54 a.m. |
| PDg | Predicate description generation | batch_6a004868cf308190a2a93c32c92f22d9 |
completed | May 10, 2026, 8:57 a.m. |
Created at: April 27, 2026, 2:39 p.m.