Triple
T29020000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Archaeplastida |
E737423
|
entity |
| Predicate | alternativeNameUsedInSomeLiterature |
P46176
|
FINISHED |
| Object | Plantae sensu lato |
—
|
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: Plantae sensu lato | Statement: [Archaeplastida, alternativeNameUsedInSomeLiterature, Plantae sensu lato]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alternativeNameUsedInSomeLiterature Context triple: [Archaeplastida, alternativeNameUsedInSomeLiterature, Plantae sensu lato]
-
A.
termAlsoUsedFor
chosen
Indicates that one term is also used to refer to the same or closely related concept as another term.
-
B.
alternativeUsedBy
Indicates that one entity serves as an alternative option or substitute that is used in place of another entity.
-
C.
eraNameUsedInDocuments
Indicates that a particular era name is used as a temporal reference in the specified documents.
-
D.
alternativeAbbreviation
Indicates that one term serves as an alternative shortened form or acronym for another term.
-
E.
historicalNameUsedIn
Indicates that a historical or former name was used to refer to a particular entity in some context.
- 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_69f077ee19f881909af48f9cab00a2e5 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f6978fe97081908fe568091ad9b159 |
completed | May 3, 2026, 12:32 a.m. |
| PD | Predicate disambiguation | batch_69f69661e6ec8190948251c7516a32ad |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 28, 2026, 9:48 a.m.