Triple
T14689294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Reach |
E344996
|
entity |
| Predicate | regionalSymbol |
P49410
|
FINISHED |
| Object | 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: rose | Statement: [The Reach, regionalSymbol, rose]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionalSymbol Context triple: [The Reach, regionalSymbol, rose]
-
A.
regionallySymbolicIn
chosen
Indicates that something serves as a symbol or emblem specifically within a particular region or geographic area.
-
B.
isRegional
Indicates that something pertains to, is characteristic of, or is limited to a specific geographic region or area.
-
C.
regionalComponent
Indicates that one entity functions as a sub-region or constituent part within the larger geographic or administrative area represented by the other entity.
-
D.
regionallyAssociatedWith
Indicates that two entities are connected or related based on sharing the same or overlapping geographic or regional context.
-
E.
regionalVariantOf
Indicates that one entity is a version or form of another that is specific to a particular geographic region or locale.
- 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_69d822e34b348190ada4d1cdb6c7c226 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb5844de481908a796eaa474bfde9 |
completed | April 14, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69de6579fb7881909becc8f5822b39d4 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:28 a.m.