Triple
T6850511
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GreenSet |
E158002
|
entity |
| Predicate | usedOnCourtType |
P45848
|
FINISHED |
| Object | outdoor tennis court |
—
|
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: outdoor tennis court | Statement: [GreenSet, usedOnCourtType, outdoor tennis court]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedOnCourtType Context triple: [GreenSet, usedOnCourtType, outdoor tennis court]
-
A.
usesHomeCourtFormat
Indicates that a competition or series is organized using a format where one participant gains the advantage of playing on their designated home court or venue.
-
B.
usedInSport
Indicates that something (such as an object, technique, or concept) is employed or utilized within the context of a particular sport.
-
C.
basedOnSport
Indicates that something is determined, derived, or organized according to a particular sport or sporting activity.
-
D.
hasTennisCourt
chosen
Indicates that one entity possesses, includes, or provides access to a tennis court as part of its facilities or attributes.
-
E.
alsoUsedForSport
Indicates that something primarily associated with one purpose is additionally used for sporting activities or athletic purposes.
- 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_69c6882fae988190864cbba788c5ebb4 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d84c45708190918adfc028252400 |
completed | March 27, 2026, 7:19 p.m. |
| PD | Predicate disambiguation | batch_69c6d0a12834819097d7e6c0b823745e |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:20 p.m.