Triple
T25271969
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Morelia spilota |
E633590
|
entity |
| Predicate | hasFeedingStrategy |
P84287
|
FINISHED |
| Object | constriction |
—
|
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: constriction | Statement: [Morelia spilota, hasFeedingStrategy, constriction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFeedingStrategy Context triple: [Morelia spilota, hasFeedingStrategy, constriction]
-
A.
includesFeedingType
Indicates that one entity encompasses or specifies a particular type or category of feeding associated with another entity.
-
B.
hasFeederArea
Indicates that one entity serves as the source or contributing area that supplies resources, inputs, or influence to another entity.
-
C.
hasFeederUnion
Indicates that an entity is associated with or connected to a feeder union, typically one that supplies members, resources, or support to it.
-
D.
feedingType
Indicates the manner or method by which one entity provides nourishment or food to another.
-
E.
notableFeedingBehavior
chosen
Indicates a characteristic way or pattern in which an entity typically obtains or consumes food that is considered distinctive or noteworthy.
- 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_69e75a92f48881909974ff9c11150a2e |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f48ba2bb608190bb26a5a496fff3b8 |
completed | May 1, 2026, 11:16 a.m. |
| PD | Predicate disambiguation | batch_69f4806d93dc8190b9dff4c63186faff |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 1:16 p.m.