Triple
T231490
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Statuary Hall |
E4419
|
entity |
| Predicate | statuesPlacement |
P1646
|
FINISHED |
| Object | some statues relocated to other areas of the Capitol |
—
|
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: some statues relocated to other areas of the Capitol | Statement: [Statuary Hall, statuesPlacement, some statues relocated to other areas of the Capitol]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statuesPlacement Context triple: [Statuary Hall, statuesPlacement, some statues relocated to other areas of the Capitol]
-
A.
statueHeight
Indicates the height measurement of a statue in some specified unit.
-
B.
hasStatue
chosen
Indicates that one entity possesses, contains, or is associated with a statue representing or located within it.
-
C.
veneratedAt
Indicates that an entity is honored, revered, or worshipped at a particular place or institution.
-
D.
significantMonument
Indicates that something is a monument of notable historical, cultural, or symbolic importance.
-
E.
museumAt
Indicates that an entity (such as an exhibit, artifact, or event) is located at or associated with a particular museum.
- 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_69a257363ffc81909757bde7ab3404da |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25e0868708190ad551ca06cc57f4a |
completed | Feb. 28, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69a25b5a075081909b0e9b88c1492d5a |
completed | Feb. 28, 2026, 3:04 a.m. |
Created at: Feb. 28, 2026, 2:53 a.m.