Triple
T37620323
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Palmetto Bowl |
E936048
|
entity |
| Predicate | stateSymbolReference |
P82723
|
FINISHED |
| Object | palmetto tree |
—
|
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: palmetto tree | Statement: [Palmetto Bowl, stateSymbolReference, palmetto tree]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stateSymbolReference Context triple: [Palmetto Bowl, stateSymbolReference, palmetto tree]
-
A.
symbolForState
chosen
Indicates that one entity serves as the symbolic representation (such as an icon, emblem, or notation) used to denote or stand for a particular state of another entity.
-
B.
symbolReferenced
Indicates that one symbol is mentioned, cited, or otherwise referred to by another symbol.
-
C.
symbolicallyStates
Indicates that one entity expresses or asserts something in a symbolic or representational form rather than in a direct or literal manner.
-
D.
referenceState
Indicates that one entity serves as a reference or baseline state against which another entity’s state is defined, compared, or interpreted.
-
E.
refersToStateOf
Indicates that one entity denotes, describes, or is about the condition, status, or situation (state) of another entity.
- 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_69f76ed16b748190ad6add183b1be688 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fefb15220081908da36aac386fa582 |
completed | May 9, 2026, 9:15 a.m. |
| PD | Predicate disambiguation | batch_69fefa8e8ad48190a723fed81e9d64d0 |
completed | May 9, 2026, 9:12 a.m. |
Created at: May 3, 2026, 4:18 p.m.