Triple
T23641379
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | African oystercatcher |
E583902
|
entity |
| Predicate | usesBillFor |
P153003
|
FINISHED |
| Object | opening mussels |
—
|
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: opening mussels | Statement: [African oystercatcher, usesBillFor, opening mussels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesBillFor Context triple: [African oystercatcher, usesBillFor, opening mussels]
-
A.
usesBillingModel
Indicates that one entity applies or operates under a particular billing model for charging or pricing purposes.
-
B.
chargesFeeFor
Indicates that one entity requires payment of a fee from another entity in exchange for a specific service, product, or privilege.
-
C.
chargesWere
Indicates that specific accusations or legal charges existed or were formally brought against an entity at some point in time.
-
D.
chargesBasedOn
Indicates that one party determines or applies a fee, price, or cost to another party or item according to a specified basis, criterion, or reference.
-
E.
billedBy
Indicates that one entity issues a bill or invoice to another entity for goods, services, or charges.
- 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_69e248fe1c2c8190ac914d2442ff3d26 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b28152108190972ac680cba986d7 |
completed | April 29, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f118d7903c8190bb590a71771e93af |
completed | April 28, 2026, 8:30 p.m. |
| PDg | Predicate description generation | batch_69f1233300bc8190ac1639bdca1d7d99 |
completed | April 28, 2026, 9:14 p.m. |
Created at: April 17, 2026, 6:48 p.m.