Triple
T10229832
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Code of Nomenclature for algae, fungi, and plants |
E243308
|
entity |
| Predicate | governsRank |
P58612
|
FINISHED |
| Object | species |
—
|
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: species | Statement: [International Code of Nomenclature for algae, fungi, and plants, governsRank, species]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governsRank Context triple: [International Code of Nomenclature for algae, fungi, and plants, governsRank, species]
-
A.
grantsRank
Indicates that one entity confers or assigns a particular rank, status, or level to another entity.
-
B.
rankingScope
Indicates the context or domain within which a ranking is defined, interpreted, or applied.
-
C.
usesRank
Indicates that one entity applies or relies on a ranking or ordered level system associated with another entity.
-
D.
governmentalRank
Indicates the official hierarchical level or position an entity holds within a governmental or public administration structure.
-
E.
canonicalRank
chosen
Indicates the standard or officially recognized rank or level assigned to an entity within an ordered hierarchy.
- 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_69d381b0f97c819085c9b45799a5fb7c |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d23b620c8190b8a72d0eb0d16b93 |
completed | April 7, 2026, 9:45 a.m. |
| PD | Predicate disambiguation | batch_69d4d1e9798c8190b437d53d48554ba1 |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:19 a.m.