Triple
T35096645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maoutia puya |
E1012882
|
entity |
| Predicate | hasChorotype |
P198069
|
FINISHED |
| Object | East Asian element |
—
|
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: East Asian element | Statement: [Maoutia puya, hasChorotype, East Asian element]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChorotype Context triple: [Maoutia puya, hasChorotype, East Asian element]
-
A.
isChoraOf
Indicates a relationship where one entity is the chora (a surrounding or subordinate territory/space) associated with another entity, typically a central place or polis.
-
B.
hasArchetype
Indicates that one entity serves as the original model, pattern, or prototype upon which another entity is based or conceptually derived.
-
C.
hasHumanCharacteristic
Indicates that an entity possesses a trait, quality, or behavior typically associated with humans.
-
D.
hasChromosomeType
Indicates a relationship where an entity is associated with or characterized by a specific type or category of chromosome.
-
E.
hasEthnicCharacteristic
Indicates that an entity possesses or is associated with a particular ethnic characteristic or identity.
- 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_69f76dd432ec8190969bc32acfc152b1 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fec5c503808190bde0b1829ea43071 |
completed | May 9, 2026, 5:27 a.m. |
| PD | Predicate disambiguation | batch_69fec535dd6c8190a6ab85201f5a04a9 |
completed | May 9, 2026, 5:25 a.m. |
| PDg | Predicate description generation | batch_69fec5c3f8248190b835a8e4eba470c4 |
completed | May 9, 2026, 5:27 a.m. |
Created at: May 3, 2026, 4:01 p.m.