Triple
T38193318
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Upper Creek |
E1005535
|
entity |
| Predicate | maySupportActivity |
P2186
|
FINISHED |
| Object | freshwater fishing |
—
|
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: freshwater fishing | Statement: [Upper Creek, maySupportActivity, freshwater fishing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maySupportActivity Context triple: [Upper Creek, maySupportActivity, freshwater fishing]
-
A.
supportsActivity
chosen
Indicates that one entity provides the necessary conditions, resources, or environment for another entity’s activity to occur or be sustained.
-
B.
mayRestrictActivity
Indicates that one entity has the authority or ability to limit, constrain, or prohibit certain actions or behaviors of another entity.
-
C.
supportedAct
Indicates that one entity provided assistance, endorsement, or backing for a particular action or activity performed by another entity.
-
D.
mayApply
Indicates that an entity is permitted or eligible to submit or use something (such as a rule, action, or resource) under certain conditions.
-
E.
mayEngageIn
Indicates that one entity is permitted or authorized to participate in or perform a particular activity or interaction with 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_69f76dbd22f48190940318cea061e8bb |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fcc42cbac48190b8d3e4c9ce140838 |
completed | May 7, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69fcb0fc69c88190800453eb57a7e62c |
completed | May 7, 2026, 3:34 p.m. |
Created at: May 3, 2026, 4:29 p.m.