Triple
T6143225
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | J. H. Frankland |
E137011
|
entity |
| Predicate | describesAccordingTo |
P264
|
FINISHED |
| Object | rules of botanical nomenclature |
—
|
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: rules of botanical nomenclature | Statement: [J. H. Frankland, describesAccordingTo, rules of botanical nomenclature]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: describesAccordingTo Context triple: [J. H. Frankland, describesAccordingTo, rules of botanical nomenclature]
-
A.
describes
chosen
Indicates that one entity provides an explanation, representation, or account of another entity or concept.
-
B.
describedIn
Indicates that information about an entity is contained or documented within a specified source, such as a text, document, or media.
-
C.
describesCharacteristicOf
Indicates that one entity expresses or specifies a characteristic, feature, or property of another entity.
-
D.
basedOnDescription
Indicates that one entity is derived, determined, or inferred from the description or textual details of another entity.
-
E.
describesSearchFor
Indicates that one entity provides a description or characterization of another entity’s act of searching for something.
- 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_69c008a2c6308190a56519b22d55d083 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05cb50cb0819081ac64becf7aaf55 |
completed | March 22, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69c055f39e0881909ae56444b1b48929 |
completed | March 22, 2026, 8:49 p.m. |
Created at: March 22, 2026, 4:16 p.m.