Triple
T33254056
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Botanical Congress |
E851327
|
entity |
| Predicate | formerlyDecidedOn |
P200864
|
FINISHED |
| Object | International Code of Botanical Nomenclature |
—
|
NE NERFINISHED |
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: International Code of Botanical Nomenclature | Statement: [International Botanical Congress, formerlyDecidedOn, International Code of Botanical Nomenclature]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerlyDecidedOn Context triple: [International Botanical Congress, formerlyDecidedOn, International Code of Botanical Nomenclature]
-
A.
decidedBefore
Indicates that one decision or choice was made earlier in time than another decision or choice.
-
B.
decidedIn
Indicates that a decision, ruling, or outcome was made within a particular case, proceeding, or deliberative context.
-
C.
decidedWith
Indicates that an entity made a decision jointly or in agreement with another entity.
-
D.
wasDecidedBy
Indicates that a decision or outcome was determined or resolved by a specific agent or authority.
-
E.
decidedUnder
Indicates that a decision or outcome is made within the authority, rules, or jurisdiction of a particular entity or context.
- 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_69f34963135c819084e7f1d483421f00 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ffb5c373948190a6606e8caa87a384 |
completed | May 9, 2026, 10:31 p.m. |
| PD | Predicate disambiguation | batch_69ffb261da788190b41399df8ed895e8 |
completed | May 9, 2026, 10:17 p.m. |
| PDg | Predicate description generation | batch_69ffb5c2cef0819087a92a1a5ab694a8 |
completed | May 9, 2026, 10:31 p.m. |
Created at: May 1, 2026, 1:31 a.m.