Triple
T26708411
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monarcha |
E673341
|
entity |
| Predicate | hasBillAdaptation |
P165362
|
FINISHED |
| Object | adapted for catching insects in flight |
—
|
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 catching insects in flight | Statement: [Monarcha, hasBillAdaptation, adapted for catching insects in flight]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBillAdaptation Context triple: [Monarcha, hasBillAdaptation, adapted for catching insects in flight]
-
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.
isAdaptation
Indicates that one work is derived from, based on, or reinterprets the content of another work.
-
C.
hasLaterAdaptation
Indicates that one work has been adapted into another work that was created or released at a later time.
-
D.
isAdaptive
Indicates that an entity can adjust or modify its behavior, structure, or response in reaction to changing conditions or inputs.
-
E.
hasAdaptationsIn
Indicates that something possesses or exhibits adaptations within a particular context, environment, or domain.
- 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_69eecda3a22881908f3061c760b9d542 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f658a91ba0819084fbe3dd8a09f7cd |
completed | May 2, 2026, 8:03 p.m. |
| PD | Predicate disambiguation | batch_69f6575ba12081909396036f78757a76 |
completed | May 2, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f657f2c8b08190bfeb3173ef78207d |
completed | May 2, 2026, 8 p.m. |
Created at: April 27, 2026, 3:35 a.m.