Triple
T26257383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Capitol Grounds sculpture |
E656746
|
entity |
| Predicate | visibleInPlace |
P9694
|
FINISHED |
| Object | Capitol Grounds |
—
|
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: Capitol Grounds | Statement: [Capitol Grounds sculpture, visibleInPlace, Capitol Grounds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: visibleInPlace Context triple: [Capitol Grounds sculpture, visibleInPlace, Capitol Grounds]
-
A.
visibleAt
chosen
Indicates that one entity can be seen or perceived from a specific location, viewpoint, or context at a given time.
-
B.
visibleUnder
Indicates that one entity can be seen or perceived when another specified condition, context, or covering entity is present or in effect.
-
C.
visibleAfter
Indicates that one entity becomes perceptible or can be seen only after another specified event, time, or condition has occurred.
-
D.
visibleByDefault
Indicates that something is initially shown or accessible without requiring any additional action or configuration to make it visible.
-
E.
apparentIn
Indicates that something is visibly present, manifested, or evident within or through another thing or context.
- 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_69ee5b4d25ac819086acb51184602576 |
completed | April 26, 2026, 6:37 p.m. |
| NER | Named-entity recognition | batch_69f60dfbd8e48190b450a6eb5873f021 |
completed | May 2, 2026, 2:45 p.m. |
| PD | Predicate disambiguation | batch_69f5f7ff548c8190a23e98c5e66e0bc7 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 9:09 p.m.