Triple
T27499061
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old World sparrows |
E694097
|
entity |
| Predicate | typicalBillAdaptation |
P142817
|
FINISHED |
| Object | seed-eating |
—
|
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: seed-eating | Statement: [Old World sparrows, typicalBillAdaptation, seed-eating]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalBillAdaptation Context triple: [Old World sparrows, typicalBillAdaptation, seed-eating]
-
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.
billAdaptationFor
Indicates that a legislative bill is created or modified specifically to implement, support, or regulate a particular adaptation or adjustment.
-
C.
adaptationType
Indicates the specific kind or category of adaptation that relates one entity to another or to a particular context.
-
D.
hasBillAdaptation
Indicates that an entity has a related adaptation in the form of a bill or legislative proposal.
-
E.
typicalAdaptations
chosen
Indicates the characteristic adaptations or traits that are commonly associated with or typical for an entity in a given context.
- 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_69ef538370888190b1ddf53bb4831188 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69ffb69812808190a751853b30183e65 |
completed | May 9, 2026, 10:35 p.m. |
| PD | Predicate disambiguation | batch_69ffb63bdda88190a9dd8426dc0bad43 |
completed | May 9, 2026, 10:33 p.m. |
Created at: April 27, 2026, 1:10 p.m.