Triple
T27505630
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paradoxornithidae |
E694270
|
entity |
| Predicate | typicalBillDescription |
P200916
|
FINISHED |
| Object | parrot-like bill |
—
|
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: parrot-like bill | Statement: [Paradoxornithidae, typicalBillDescription, parrot-like bill]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalBillDescription Context triple: [Paradoxornithidae, typicalBillDescription, parrot-like bill]
-
A.
typicalBillet
Indicates that something serves as a standard or characteristic billet or assignment for a given role, context, or entity.
-
B.
typicalOnsetDescription
Indicates the usual or characteristic way in which a condition, event, or process begins or first presents itself.
-
C.
typicalRate
Indicates the standard or commonly expected rate at which something occurs, is charged, or is applied in a given context.
-
D.
typicalBilletsInclude
Indicates that certain items or roles are commonly or normally included within a given set of billets.
-
E.
usesBillFor
Indicates that one entity employs, relies on, or makes use of a particular bill (such as a legislative proposal, invoice, or statement) for a specific purpose or action.
- 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_69ef538370888190b1ddf53bb4831188 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69ffb97b8ff8819088b105d99a0820c9 |
completed | May 9, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69ffb88ef7388190a710120ed76edc0e |
completed | May 9, 2026, 10:43 p.m. |
| PDg | Predicate description generation | batch_69ffb97ae1508190bf3addd6e2aac281 |
completed | May 9, 2026, 10:47 p.m. |
Created at: April 27, 2026, 1:13 p.m.