Triple
T35122289
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asian openbill |
E1014193
|
entity |
| Predicate | billAdaptationFor |
P182553
|
FINISHED |
| Object | feeding on aquatic snails |
—
|
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: feeding on aquatic snails | Statement: [Asian openbill, billAdaptationFor, feeding on aquatic snails]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: billAdaptationFor Context triple: [Asian openbill, billAdaptationFor, feeding on aquatic snails]
-
A.
billAdaptation
Indicates that a bill or legislative proposal has been modified or adjusted, typically in response to feedback, new information, or changing conditions.
-
B.
hasBillAdaptation
Indicates that an entity has a related adaptation in the form of a bill or legislative proposal.
-
C.
billType
Indicates the classification or category assigned to a bill (such as its kind, purpose, or procedural type).
-
D.
payReform
Indicates a relationship where an authority changes or restructures the pay system, such as salaries or compensation terms, for a group of people.
-
E.
billing
Indicates that one entity charges another entity for goods or services, typically by issuing an invoice or request for payment.
- 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_69f76dd8b6948190aaa32b081816bd94 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78dbf72648190a4971a558e9d1889 |
completed | May 3, 2026, 6:02 p.m. |
| PD | Predicate disambiguation | batch_69f78b8f4cc08190b49fccd798cb25d7 |
completed | May 3, 2026, 5:53 p.m. |
| PDg | Predicate description generation | batch_69f78ce43094819093857fc99f269afe |
completed | May 3, 2026, 5:59 p.m. |
Created at: May 3, 2026, 4:01 p.m.