Triple
T25989934
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queen Anne Boulevard |
E646316
|
entity |
| Predicate | isHistoricResource |
P4238
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Queen Anne Boulevard, isHistoricResource, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isHistoricResource Context triple: [Queen Anne Boulevard, isHistoricResource, true]
-
A.
includesHistoricResource
Indicates that one entity contains, encompasses, or otherwise has within its scope a historic resource.
-
B.
isHistoric
chosen
Indicates that something has significant importance or relevance in history, often due to its age, impact, or role in past events.
-
C.
hasHistoricResourceType
Indicates that an entity is associated with a particular category or type of historic resource.
-
D.
hasResourceHistory
Indicates that an entity is associated with a record or sequence of past states, usages, or changes of a particular resource over time.
-
E.
isHistoricSee
Indicates that one entity serves or functioned as a historically significant viewing point or place from which another entity is or was seen.
- 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_69e77e88cb8481908da31d4a00661f55 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6054760f08190b41fe4b710d9cc39 |
completed | May 2, 2026, 2:08 p.m. |
| PD | Predicate disambiguation | batch_69f5aff889988190ad10bcf1a280f717 |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 22, 2026, 8:56 a.m.