Triple
T13087307
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Florida Derby |
E310369
|
entity |
| Predicate | derbyNameRefersTo |
P53956
|
FINISHED |
| Object | state of Florida |
—
|
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: state of Florida | Statement: [Florida Derby, derbyNameRefersTo, state of Florida]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: derbyNameRefersTo Context triple: [Florida Derby, derbyNameRefersTo, state of Florida]
-
A.
derby
Indicates a competitive match or contest, typically between closely linked or rival entities (such as teams from the same area or group).
-
B.
symbolReferenced
chosen
Indicates that one symbol is mentioned, cited, or otherwise referred to by another symbol.
-
C.
derbyFocus
Indicates that something is the main subject, theme, or point of attention within the context of a derby event or competition.
-
D.
refersToOfficialName
Indicates that one entity is referencing or using the formally recognized, official name of another entity.
-
E.
derbyInvolves
Indicates that a particular derby event includes or features the participation of a specified entity or entities.
- 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_69d806a733548190989cfd4ce981ca33 |
completed | April 9, 2026, 8:05 p.m. |
| NER | Named-entity recognition | batch_69d981378dd08190b4f00e4e5df0e480 |
completed | April 10, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69d9803f6c508190bfadfbc2d00c2c64 |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9:02 p.m.