Triple
T27257390
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Troitsky (Trinity) Cathedral area |
E687662
|
entity |
| Predicate | hasViewDominatedBy |
P169934
|
FINISHED |
| Object | Trinity Cathedral dome |
—
|
NE NERFINISHED |
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: Trinity Cathedral dome | Statement: [Troitsky (Trinity) Cathedral area, hasViewDominatedBy, Trinity Cathedral dome]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasViewDominatedBy Context triple: [Troitsky (Trinity) Cathedral area, hasViewDominatedBy, Trinity Cathedral dome]
-
A.
hasDominated
Indicates that one entity has exercised overwhelming control, superiority, or influence over another, often in a sustained or decisive manner.
-
B.
isDynamicallyDominatedBy
Indicates that one entity’s behavior, control flow, or outcome is constrained or overridden by another entity during runtime execution.
-
C.
dominatedBy
Indicates that one entity is under the control, influence, or overpowering authority of another entity.
-
D.
hasDominantTree
Indicates that one tree in a given context or area is the primary or most influential tree relative to others.
-
E.
hasView
Indicates that one entity provides a visual perspective or outlook onto another entity or scene.
- 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_69ef35567e808190a94458cd44ebff0c |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f688d015908190ad5df37030ecf332 |
completed | May 2, 2026, 11:29 p.m. |
| PD | Predicate disambiguation | batch_69f68609c0b08190a8e1238a4d97c270 |
completed | May 2, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69f688034580819086a0f9100645f8ba |
completed | May 2, 2026, 11:25 p.m. |
Created at: April 27, 2026, 10:50 a.m.