Triple
T11634696
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rosoideae |
E276485
|
entity |
| Predicate | notableOrnamental |
P100111
|
FINISHED |
| Object | garden roses |
—
|
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: garden roses | Statement: [Rosoideae, notableOrnamental, garden roses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableOrnamental Context triple: [Rosoideae, notableOrnamental, garden roses]
-
A.
notableOrdinary
Indicates that an entity is notable or significant despite being otherwise ordinary or typical in its category.
-
B.
notableSculpture
Indicates that an entity is a sculpture for which the subject is especially known or recognized.
-
C.
notableOde
Indicates that one entity is an ode that is notably associated with, or distinguished in relation to, another entity.
-
D.
notableElement
Indicates that an entity has a component, feature, or part that is especially significant, prominent, or noteworthy in relation to it.
-
E.
notableRelic
Indicates that an entity is a historically or culturally significant relic associated with another entity (such as a place, person, or event).
- 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_69d6aafa51148190ab84940694c00235 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a25c0b00819095898d2b2445ecfb |
completed | April 10, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69d85dd94bdc819091fa2ed33eb31624 |
completed | April 10, 2026, 2:18 a.m. |
| PDg | Predicate description generation | batch_69d87f30642c8190ad94fa061cde186b |
completed | April 10, 2026, 4:40 a.m. |
Created at: April 8, 2026, 9:39 p.m.