Triple
T29888518
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parrot’s Beak |
E759079
|
entity |
| Predicate | typicalHabitatOfPlantsSoNamed |
P8732
|
FINISHED |
| Object | warm climates |
—
|
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: warm climates | Statement: [Parrot’s Beak, typicalHabitatOfPlantsSoNamed, warm climates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalHabitatOfPlantsSoNamed Context triple: [Parrot’s Beak, typicalHabitatOfPlantsSoNamed, warm climates]
-
A.
typicalVegetationAdaptation
Indicates the characteristic ways in which vegetation is adapted to the prevailing environmental conditions of a given area.
-
B.
growsIn
chosen
Indicates that one entity develops, thrives, or increases in size or number within a specified environment, medium, or location.
-
C.
vegetationType
Indicates the specific kind or category of plant cover or flora that characterizes a given area or environment.
-
D.
growsOn
Indicates that one entity develops or increases in size, number, or extent while being physically supported by or attached to another entity.
-
E.
typicalHabitatInHost
Indicates that an organism’s usual or characteristic habitat occurs within a particular host organism.
- 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_69f2245de2f48190a481404896b56254 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_6a030f1480148190a5e8c8926ded252c |
completed | May 12, 2026, 11:29 a.m. |
| PD | Predicate disambiguation | batch_6a030e7f5fa481909696733defefcc20 |
completed | May 12, 2026, 11:26 a.m. |
Created at: April 29, 2026, 6:01 p.m.