Triple
T7796983
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Passeridae |
E180323
|
entity |
| Predicate | typicalBillType |
P21527
|
FINISHED |
| Object | conical 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: conical bill | Statement: [Passeridae, typicalBillType, conical bill]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalBillType Context triple: [Passeridae, typicalBillType, conical bill]
-
A.
billType
chosen
Indicates the classification or category assigned to a bill (such as its kind, purpose, or procedural type).
-
B.
chargeType
Indicates the category or nature of a charge applied in a transaction or interaction between entities (e.g., fee type, billing classification, or legal charge type).
-
C.
feeType
Indicates the specific category or classification of a fee associated with a transaction, service, or obligation.
-
D.
patronType
Indicates the classification or category of a patron in relation to a service, institution, or resource.
-
E.
moneyBillRecommendation
Indicates that one entity formally recommends or proposes a money bill or financial legislation to another authority or body.
- 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_69ca827d22208190b4dc5aa680edcf5d |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69caf78a6d88819093f83528fe88b182 |
completed | March 30, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69cae9111b2481909684a2d4aa4831c2 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:32 p.m.