Triple
T332171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Black-eyed Susan |
E6647
|
entity |
| Predicate | centerType |
P11544
|
FINISHED |
| Object | disk florets |
—
|
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: disk florets | Statement: [Black-eyed Susan, centerType, disk florets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centerType Context triple: [Black-eyed Susan, centerType, disk florets]
-
A.
centralIn
Indicates that one entity occupies a central or most important position within another entity, context, or structure.
-
B.
centralText
Indicates that one text element is positioned or designated as the central or primary text relative to surrounding content or layout.
-
C.
isCentralTo
Indicates that something plays a primary, essential, or defining role in relation to something else, such that the latter depends on or is organized around it.
-
D.
isMajorCenterOf
Indicates that a place serves as a primary hub or focal point for a particular activity, function, or domain.
-
E.
regionType
Indicates the classification or category of a region, specifying what kind of region it is (e.g., administrative, geographic, or functional).
- 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_69a2e79434908190a9d5afe415153ad9 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2eab1a7048190ac690ddc2e294914 |
completed | Feb. 28, 2026, 1:16 p.m. |
| PD | Predicate disambiguation | batch_69a2e94c6d8881908239d3788c018adf |
completed | Feb. 28, 2026, 1:10 p.m. |
| PDg | Predicate description generation | batch_69a2ea09a5e881908b313cb37409a4f9 |
completed | Feb. 28, 2026, 1:13 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.