Triple
T8757035
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Takhtajan system |
E208095
|
entity |
| Predicate | classificationLevelUsed |
P14125
|
FINISHED |
| Object | class |
—
|
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: class | Statement: [Takhtajan system, classificationLevelUsed, class]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: classificationLevelUsed Context triple: [Takhtajan system, classificationLevelUsed, class]
-
A.
classificationLevel
Indicates the degree or tier within an ordered system or hierarchy to which something is assigned for categorization or control purposes.
-
B.
classLevel
Indicates the academic or hierarchical level associated with a particular class within an educational or organizational structure.
-
C.
designationLevel
chosen
Indicates the specific rank, tier, or level assigned to an entity within a designation or classification system.
-
D.
codificationLevel
Indicates the degree or extent to which something is formally systematized, standardized, or encoded into an explicit set of rules or structures.
-
E.
classificationUsedBy
Indicates that a particular classification system or scheme is employed or applied by a given 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_69ca835cd6b08190bd7c63db92f53c86 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5ddabdc88190ba50ef1833a815d0 |
completed | March 31, 2026, 11:50 p.m. |
| PD | Predicate disambiguation | batch_69cc5c160dac8190b4aeb4bf0529de52 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:40 p.m.