Triple
T14500547
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pouzolzia heterophylla |
E359621
|
entity |
| Predicate | isTropicalSpecies |
P50850
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Pouzolzia heterophylla, isTropicalSpecies, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTropicalSpecies Context triple: [Pouzolzia heterophylla, isTropicalSpecies, true]
-
A.
isTropical
chosen
Indicates that something belongs to, occurs in, or is characteristic of tropical regions or climates.
-
B.
isPlantOf
Indicates that one entity is a plant that belongs to, is associated with, or is characteristic of another entity (such as a region, habitat, or owner).
-
C.
isInlandVarietyOf
Indicates that one entity is a variety or subtype of another that occurs specifically in inland (non-coastal) areas.
-
D.
isBotanical
Indicates that something pertains to plants or plant science, such as being derived from, related to, or characteristic of botanical life or botany.
-
E.
isWoodyPlant
Indicates that the subject is a plant characterized by persistent, woody stems or trunks that remain above ground year-round.
- 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_69d8279740308190af9df93a3af8592e |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de94dfe484819086dd971606e6478e |
completed | April 14, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69de5c4ccba08190a988bfda0bc9f5cb |
completed | April 14, 2026, 3:25 p.m. |
Created at: April 10, 2026, 1:21 a.m.