Triple
T9570112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Linnaean sexual system of plants |
E230891
|
entity |
| Predicate | classDefinitionBasedOn |
P64521
|
FINISHED |
| Object | number of stamens |
—
|
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: number of stamens | Statement: [Linnaean sexual system of plants, classDefinitionBasedOn, number of stamens]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: classDefinitionBasedOn Context triple: [Linnaean sexual system of plants, classDefinitionBasedOn, number of stamens]
-
A.
coreDefinition
Indicates the fundamental, central meaning or essence that defines something at its most basic level.
-
B.
basingConcept
chosen
Indicates that one concept serves as the foundational basis or underlying rationale for another concept.
-
C.
baseDefinedBy
Indicates that something’s foundational properties, structure, or interpretation are determined or specified by a particular base or underlying system.
-
D.
definesType
Indicates that one entity specifies or establishes the type or classification of another entity.
-
E.
isBasedOn
Indicates that one entity is derived from, inspired by, or developed using the content, structure, or principles of another entity.
- 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_69ca847f22188190a56e4a97625bef22 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd998940c881909f9025512cf72fe9 |
completed | April 1, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69ccd59b960c8190966a8870a2426bd5 |
completed | April 1, 2026, 8:21 a.m. |
Created at: March 30, 2026, 8:04 p.m.