Triple
T31714669
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rockport, Texas |
E809420
|
entity |
| Predicate | birdingTrailSite |
P172458
|
FINISHED |
| Object | Great Texas Coastal Birding Trail |
—
|
NE NERFINISHED |
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: Great Texas Coastal Birding Trail | Statement: [Rockport, Texas, birdingTrailSite, Great Texas Coastal Birding Trail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: birdingTrailSite Context triple: [Rockport, Texas, birdingTrailSite, Great Texas Coastal Birding Trail]
-
A.
birdwatchingFeature
Indicates a feature, characteristic, or amenity that is specifically related to or beneficial for birdwatching activities.
-
B.
birdSanctuaryLocatedOn
Indicates that a bird sanctuary is situated on or within the geographic area or property of a specified location.
-
C.
hasWildlifeObservationPoints
Indicates that a location or area includes designated points or spots where wildlife can be observed.
-
D.
birdObservatoryStatus
Indicates the operational or functional status of a bird observatory at a given time or condition.
-
E.
birdDiversity
Indicates the variety and richness of different bird species present within a given area, community, or dataset.
- 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_69f348df4e048190a4a5a9932ada78d6 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6abe15d5c81909ccf4ce37f78bc43 |
completed | May 3, 2026, 1:58 a.m. |
| PD | Predicate disambiguation | batch_69f6aa20a1588190a53533fc9764efb2 |
completed | May 3, 2026, 1:51 a.m. |
| PDg | Predicate description generation | batch_69f6aaf31a548190b2f792ff4b8c002a |
completed | May 3, 2026, 1:54 a.m. |
Created at: April 30, 2026, 11:16 p.m.