Triple
T1927017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | White House, Moscow |
E40854
|
entity |
| Predicate | hasBasRelief |
P11199
|
FINISHED |
| Object | state emblem of Russia |
—
|
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: state emblem of Russia | Statement: [White House, Moscow, hasBasRelief, state emblem of Russia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBasRelief Context triple: [White House, Moscow, hasBasRelief, state emblem of Russia]
-
A.
hasReliefFeature
Indicates that one entity possesses or includes a specific relief-related physical feature or characteristic.
-
B.
hasRelativeRelief
Indicates a relationship where one entity is characterized by the degree of variation in elevation or relief relative to another reference entity or area.
-
C.
hasRelief
Indicates that one entity features or exhibits a raised or sculpted surface design (relief) in relation to another entity or context.
-
D.
hasReliefOf
chosen
Indicates that one entity features, bears, or is adorned with a sculpted or carved relief representation of another entity.
-
E.
hasStatue
Indicates that one entity possesses, contains, or is associated with a statue representing or located within it.
- 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_69a8864711648190b07bed24ed76258e |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb263cdb8819084d0bda98a2a71e0 |
completed | March 7, 2026, 5:06 a.m. |
| PD | Predicate disambiguation | batch_69abafeec6f881909d47acb966683279 |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:35 p.m.