Triple
T277017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Munroe Tavern |
E5270
|
entity |
| Predicate | isPreservedAs |
P7647
|
FINISHED |
| Object | historic landmark |
—
|
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: historic landmark | Statement: [Munroe Tavern, isPreservedAs, historic landmark]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPreservedAs Context triple: [Munroe Tavern, isPreservedAs, historic landmark]
-
A.
preservedAt
Indicates that something is kept, maintained, or conserved in a particular place or context.
-
B.
isUsedAs
Indicates that one entity serves a particular function, role, or purpose as another entity.
-
C.
reservedFor
Indicates that something is set aside or allocated specifically for the use, benefit, or purpose of a particular entity or group.
-
D.
protectedAs
chosen
Indicates that one entity is safeguarded, preserved, or kept safe by another entity or under a specified protective status or mechanism.
-
E.
reconstructedAs
Indicates that one entity has been rebuilt, recreated, or inferred based on evidence, models, or partial information from another entity.
- 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_69a257e6c8788190987dfe705ca2912a |
completed | Feb. 28, 2026, 2:50 a.m. |
| NER | Named-entity recognition | batch_69a25ded68c88190b1fc595ce329aeb9 |
completed | Feb. 28, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69a25b7480e881909399beccfc7ffb81 |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:59 a.m.