Triple
T6664295
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tampa Bay Times Forum |
E151558
|
entity |
| Predicate | hasAlternativeSurface |
P72324
|
FINISHED |
| Object | basketball 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: basketball court | Statement: [Tampa Bay Times Forum, hasAlternativeSurface, basketball court]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAlternativeSurface Context triple: [Tampa Bay Times Forum, hasAlternativeSurface, basketball court]
-
A.
hasAlternateCut
Indicates that an entity has an alternative edited version or cut, distinct from its primary or original form.
-
B.
hasPrimarySurface
Indicates that one entity serves as the main or principal surface associated with another entity.
-
C.
hasSurfaceSections
Indicates that an entity is composed of or divided into distinct sections or parts of its surface.
-
D.
hasAlternativeReferent
Indicates that an entity can also be referred to or identified by an alternative name, label, or reference.
-
E.
hasSurfaceQuality
Indicates that one entity possesses a particular characteristic or condition of its surface.
- 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_69c687f5fac48190a09e4838d9c6b45d |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6ce738fe88190a5557900efeec7ec |
completed | March 27, 2026, 6:37 p.m. |
| PD | Predicate disambiguation | batch_69c6ad09974c81908784300ae218961f |
completed | March 27, 2026, 4:15 p.m. |
| PDg | Predicate description generation | batch_69c6ce72809c8190be85f6e42ca1c8ea |
completed | March 27, 2026, 6:37 p.m. |
Created at: March 27, 2026, 2:02 p.m.