Triple
T8025259
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ciconiiformes |
E186837
|
entity |
| Predicate | billAdaptation |
P80640
|
FINISHED |
| Object | adapted for probing or grasping aquatic prey |
—
|
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: adapted for probing or grasping aquatic prey | Statement: [Ciconiiformes, billAdaptation, adapted for probing or grasping aquatic prey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: billAdaptation Context triple: [Ciconiiformes, billAdaptation, adapted for probing or grasping aquatic prey]
-
A.
billType
Indicates the classification or category assigned to a bill (such as its kind, purpose, or procedural type).
-
B.
billColor
Indicates the color attribute associated with the bill (beak) of an entity.
-
C.
isAdaptation
Indicates that one work is derived from, based on, or reinterprets the content of another work.
-
D.
billing
Indicates that one entity charges another entity for goods or services, typically by issuing an invoice or request for payment.
-
E.
adjustmentType
Indicates the specific kind or category of modification applied to an existing value, state, or configuration within the relationship.
- 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_69ca82ad4e2c8190a693e3c9e30fe66f |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3ec9983c8190b468c13f5b5beb63 |
completed | March 31, 2026, 3:26 a.m. |
| PD | Predicate disambiguation | batch_69cb049253d08190bafcecfde493ab8b |
completed | March 30, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69cb14bcbbc0819094a98e7ffffb7a40 |
completed | March 31, 2026, 12:26 a.m. |
Created at: March 30, 2026, 5:21 p.m.