Triple
T33173397
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Friendship Heights, Maryland |
E849095
|
entity |
| Predicate | shoppingCenters |
P127620
|
FINISHED |
| Object | Chevy Chase Pavilion |
—
|
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: Chevy Chase Pavilion | Statement: [Friendship Heights, Maryland, shoppingCenters, Chevy Chase Pavilion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shoppingCenters Context triple: [Friendship Heights, Maryland, shoppingCenters, Chevy Chase Pavilion]
-
A.
shoppingCenterInstanceOf
Indicates that a specific shopping center is an instance of a particular type or class of shopping centers.
-
B.
locationOfShoppingCenter
chosen
Indicates that a specified place is the geographic location where a particular shopping center is situated.
-
C.
shoppingCenterCountry
Indicates the country in which a given shopping center is located.
-
D.
hasShoppingMall
Indicates that one entity possesses, contains, or includes a shopping mall within its area or domain.
-
E.
hasShoppingDistrict
Indicates that a place contains or is associated with a designated area where multiple shops and commercial retail activities are concentrated.
- 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_69f3495be8808190bbf427733df08aad |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6e02ba6b881908dfafc52d3b75f1c |
completed | May 3, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69f6de09c2f481909f8b2545d3208c9f |
completed | May 3, 2026, 5:32 a.m. |
Created at: May 1, 2026, 1:29 a.m.