Triple
T1274176
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barracks Row |
E15774
|
entity |
| Predicate | isDiningDestination |
P28272
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Barracks Row, isDiningDestination, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isDiningDestination Context triple: [Barracks Row, isDiningDestination, yes]
-
A.
hasRestaurant
Indicates that one entity possesses, operates, or contains a restaurant associated with it.
-
B.
diningStyle
Indicates the manner or format in which dining is conducted, such as casual, formal, buffet, or family-style.
-
C.
restaurantName
Indicates the name assigned to a restaurant as its identifying label.
-
D.
isServedAt
Indicates that something (such as food, drink, or a service) is provided or made available at a particular place or venue.
-
E.
EncounterRestaurantOpening
Indicates a situation where an entity comes across or experiences the opening or start of operations of a restaurant.
- F. None of above. chosen
Provenance (4 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_69a4935a94308190bb92555b79032824 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4c31602b8819087a57e8d390cae7a |
completed | March 1, 2026, 10:52 p.m. |
| PD | Predicate disambiguation | batch_69a4bee0be808190a8ccac6a41851fdd |
completed | March 1, 2026, 10:34 p.m. |
| PDg | Predicate description generation | batch_69a4c31400c08190a07ccb736df3bf54 |
completed | March 1, 2026, 10:52 p.m. |
Created at: March 1, 2026, 7:50 p.m.