Triple
T27379166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Centre, Alabama |
E691166
|
entity |
| Predicate | hasFishingEventType |
P186351
|
FINISHED |
| Object | crappie tournaments |
—
|
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: crappie tournaments | Statement: [Centre, Alabama, hasFishingEventType, crappie tournaments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFishingEventType Context triple: [Centre, Alabama, hasFishingEventType, crappie tournaments]
-
A.
fishingActivity
Indicates an activity where an entity engages in catching or attempting to catch fish or other aquatic organisms.
-
B.
hasFishingSpecies
Indicates that a location, body of water, or fishing area supports or contains one or more specific species that can be fished there.
-
C.
hasFishingSeason
Indicates that there is a defined time period during which fishing for a particular resource or in a particular area is permitted or regulated.
-
D.
hasShoreFishing
Indicates that a location or body of water provides opportunities or facilities for fishing from the shore.
-
E.
isFishingArea
Indicates that a location or region is designated or used as an area where fishing activities take place.
- 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_69ef52022538819081f873d0c84a6dd6 |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f7cec454a88190a9f3bbee2b856636 |
completed | May 3, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69f7c8977c288190997a892ec5f756ed |
completed | May 3, 2026, 10:13 p.m. |
| PDg | Predicate description generation | batch_69f7cec398ac819081c954a993c323ee |
completed | May 3, 2026, 10:40 p.m. |
Created at: April 27, 2026, 12:22 p.m.