Triple
T30010615
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guards Crimean War Memorial |
E762448
|
entity |
| Predicate | originallyFaced |
P201524
|
FINISHED |
| Object | north |
—
|
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: north | Statement: [Guards Crimean War Memorial, originallyFaced, north]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originallyFaced Context triple: [Guards Crimean War Memorial, originallyFaced, north]
-
A.
originallyHad
Indicates that an entity previously possessed, contained, or was associated with something before a change, loss, or transformation occurred.
-
B.
wasOriginally
Indicates that an entity had a particular state, form, type, or affiliation at an earlier time, which has since changed.
-
C.
originallyIn
Indicates that something first appeared, was created, or was initially located within a particular context, source, or place.
-
D.
originallyCoveredBy
Indicates that something was first protected, reported on, or documented by a particular source, medium, or entity before any others.
-
E.
originallyPresentedAs
Indicates that one entity was first introduced, described, or characterized in the form or manner specified by another entity.
- 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_69f2246b0c84819094f1250b6a02d277 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_6a000014497c819088d5cda3977522dd |
completed | May 10, 2026, 3:48 a.m. |
| PD | Predicate disambiguation | batch_69ffff9a52b08190be1024e0fb6fe661 |
completed | May 10, 2026, 3:46 a.m. |
| PDg | Predicate description generation | batch_6a000013004c8190a01710441f881fdc |
completed | May 10, 2026, 3:48 a.m. |
Created at: April 29, 2026, 6:44 p.m.