Triple
T16224378
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Landry’s, Inc. |
E393807
|
entity |
| Predicate | owns |
P347
|
FINISHED |
| Object | Chart House |
E393809
|
NE 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: Chart House | Statement: [Landry’s, Inc., owns, Chart House]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Chart House Context triple: [Landry’s, Inc., owns, Chart House]
-
A.
Chart House
chosen
Chart House is a fine-dining seafood and steak restaurant chain in the United States known for its scenic, often waterfront or high-elevation locations.
-
B.
Shell House
Shell House was the former Johannesburg headquarters of South Africa’s African National Congress, later renamed Luthuli House.
-
C.
Blake House
Blake House is a historic residence and notable landmark located in the City of Fairfax, Virginia.
-
D.
Clock House
Clock House is a suburban railway station in the London Borough of Bromley that provides local commuter services into central London.
-
E.
Lee House
Lee House is one of the historic townhouses that together form the Blair House complex, the official guest residence for visiting dignitaries in Washington, D.C.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d87f204df88190a8f88923decf9835 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e23d24f9688190b670cfeb73332293 |
completed | April 17, 2026, 2:01 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00079a5c1481909485e1b4a41f5d2c |
completed | May 10, 2026, 4:20 a.m. |
Created at: April 10, 2026, 5:03 a.m.