Triple
T38580424
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Podopterus |
E932228
|
entity |
| Predicate | isOrganismGroupType |
P37835
|
FINISHED |
| Object | vascular plants |
—
|
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: vascular plants | Statement: [Podopterus, isOrganismGroupType, vascular plants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOrganismGroupType Context triple: [Podopterus, isOrganismGroupType, vascular plants]
-
A.
isBySupergroup
Indicates that something (such as a work, event, or item) is created, performed, or produced by a supergroup, i.e., a group formed from members of other established groups.
-
B.
organismType
chosen
Indicates the biological classification or kind of organism that an entity is.
-
C.
discussesOrganismGroup
Indicates that an entity engages in discussion, analysis, or treatment of a particular group or category of organisms.
-
D.
includesOrganisms
Indicates that one entity contains, encompasses, or has as members one or more specified organisms.
-
E.
taxonGroup
Indicates a classification relationship where one taxon is grouped within or associated with a broader taxonomic group.
- 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdaa36f90819093f8661969990c7d |
completed | May 7, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fefc588190b063d7ea1ec87b07 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:32 p.m.