Triple
T5691034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rose of Sharon |
E125427
|
entity |
| Predicate | typicalSpread |
P40389
|
FINISHED |
| Object | 1.5–3 meters |
—
|
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: 1.5–3 meters | Statement: [Rose of Sharon, typicalSpread, 1.5–3 meters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalSpread Context triple: [Rose of Sharon, typicalSpread, 1.5–3 meters]
-
A.
typicalCrownSpread
chosen
Indicates the usual horizontal extent or width of an entity’s crown or canopy under normal growth conditions.
-
B.
typicalIn
Indicates that something commonly occurs, appears, or is found within a given context, category, or environment.
-
C.
spreadBy
Indicates that something is transmitted, dispersed, or propagated through the agency or action of a specified entity or medium.
-
D.
spreadTo
Indicates that something extends, propagates, or is transmitted from one entity, location, or context to another.
-
E.
typicalVariety
Indicates that one entity is a representative or characteristic example of the variety or type defined by another entity.
- 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_69c0082bb19c8190823a4facd3cba79b |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c029014588819094a2a0f6f9b66bab |
completed | March 22, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69c021c0e0408190ab6c3cd3f907e80f |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:44 p.m.