Triple
T13395450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tiliaceae |
E319690
|
entity |
| Predicate | wasRecognizedIn |
P109753
|
FINISHED |
| Object | traditional plant classifications |
—
|
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: traditional plant classifications | Statement: [Tiliaceae, wasRecognizedIn, traditional plant classifications]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasRecognizedIn Context triple: [Tiliaceae, wasRecognizedIn, traditional plant classifications]
-
A.
wasRecognizedAs
Indicates that an entity was formally identified, acknowledged, or designated as having a particular role, status, or quality.
-
B.
hasNotableRecognitionFor
Indicates that an entity has received notable recognition, such as awards, honors, or distinctions, specifically for another entity or achievement.
-
C.
reconocidaPor
Indicates that an entity is recognized, acknowledged, or honored by another entity.
-
D.
notableAwardRecognition
Indicates that an entity has received or been formally recognized with a notable award or honor.
-
E.
gainedRecognition
Indicates that an entity received acknowledgment, acclaim, or validation from others for its qualities, actions, or achievements.
- 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_69d806b943cc8190b6af624d385d7e12 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dba0d892d08190b1b192b93fe3d72d |
completed | April 12, 2026, 1:40 p.m. |
| PD | Predicate disambiguation | batch_69d9a03189908190a784a2755f8d81e1 |
completed | April 11, 2026, 1:13 a.m. |
| PDg | Predicate description generation | batch_69dadcce5a808190847f2a7833b67a5a |
completed | April 11, 2026, 11:44 p.m. |
Created at: April 9, 2026, 9:34 p.m.