Triple
T492971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Art Museum Steps |
E10227
|
entity |
| Predicate | inFrontOf |
P4990
|
FINISHED |
| Object | main entrance of the Philadelphia Museum of Art |
—
|
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: main entrance of the Philadelphia Museum of Art | Statement: [Art Museum Steps, inFrontOf, main entrance of the Philadelphia Museum of Art]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inFrontOf Context triple: [Art Museum Steps, inFrontOf, main entrance of the Philadelphia Museum of Art]
-
A.
facedBy
Indicates that one entity is oriented toward and directly opposite another entity, such that it is facing it.
-
B.
appearsBefore
Indicates that one entity occurs, is positioned, or is presented earlier in an ordered sequence than another entity.
-
C.
hasFront
chosen
Indicates that an entity possesses or is associated with a front-facing side, surface, or portion.
-
D.
operatedOnFront
Indicates that an action or operation was performed specifically on the front side or front-facing part of an entity.
-
E.
presentOn
Indicates that one entity is physically located on the surface or within the bounds of another entity.
- 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_69a2e847df8481909239ec08ccf1e376 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f0faab4881909f65f172198b5bd2 |
completed | Feb. 28, 2026, 1:43 p.m. |
| PD | Predicate disambiguation | batch_69a2edf7ce008190836fb6ab5ea39375 |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.