Triple
T15421887
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charlotte Sports Park |
E369398
|
entity |
| Predicate | hasOutfieldBoardwalk |
P118725
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Charlotte Sports Park, hasOutfieldBoardwalk, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOutfieldBoardwalk Context triple: [Charlotte Sports Park, hasOutfieldBoardwalk, yes]
-
A.
boardwalkType
Indicates the specific kind or classification of a boardwalk in relation to its general category or design.
-
B.
hasTransitVillage
Indicates that an entity includes, is associated with, or is the location of a designated transit-oriented village or development area.
-
C.
MonopolyBoardPositionType
Indicates the specific type or category of a position on a Monopoly board, such as property, utility, railroad, tax, or special spaces like Chance or Jail.
-
D.
hasOutdoorSpaceType
Indicates the specific kind of outdoor area associated with an entity, such as a balcony, terrace, garden, or patio.
-
E.
hasMainEquityBoard
Indicates that an entity is associated with or listed on a primary equity trading board or main stock exchange market segment.
- 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_69d85a1849f48190bf898068b2806fae |
completed | April 10, 2026, 2:02 a.m. |
| NER | Named-entity recognition | batch_69e03ebe7b1081908e6b9e6e128a8d5d |
completed | April 16, 2026, 1:43 a.m. |
| PD | Predicate disambiguation | batch_69ded27f45548190a6d2b1b85cb47444 |
completed | April 14, 2026, 11:49 p.m. |
| PDg | Predicate description generation | batch_69ded57005608190886cd01f640dfedb |
completed | April 15, 2026, 12:01 a.m. |
Created at: April 10, 2026, 3:20 a.m.