Triple
T27534628
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | White Rose of York flag |
E695063
|
entity |
| Predicate | centeredCharge |
P164508
|
FINISHED |
| Object | white rose |
—
|
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: white rose | Statement: [White Rose of York flag, centeredCharge, white rose]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centeredCharge Context triple: [White Rose of York flag, centeredCharge, white rose]
-
A.
centralCharge
Indicates that an entity has a specific central charge value, typically quantifying a key parameter in a conformal or related physical or mathematical theory.
-
B.
centralChargeDepicts
Indicates that the central charge of an object or system visually represents or symbolically depicts another entity or concept.
-
C.
hasCentralCharge
Indicates that an entity is associated with, or characterized by, a specific central charge value in a given theoretical or physical framework.
-
D.
centerIs
Indicates that one entity serves as the central point or middle position of another entity or space.
-
E.
centered
Indicates that one entity is positioned at or around the central point of another entity or reference frame.
- 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_69ef538608b081908b9f659bb09d5e0f |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f64e6e8c9081908ce4d364aa26147a |
completed | May 2, 2026, 7:20 p.m. |
| PD | Predicate disambiguation | batch_69f64cacd2c08190aed8a1761d0da679 |
completed | May 2, 2026, 7:12 p.m. |
| PDg | Predicate description generation | batch_69f64db8ee1881909362701d72ffe282 |
completed | May 2, 2026, 7:17 p.m. |
Created at: April 27, 2026, 1:28 p.m.