Triple
T32382319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asahi Flame |
E827454
|
entity |
| Predicate | locatedInTheFacility |
P37657
|
FINISHED |
| Object | Asahi Beer Hall |
E181383
|
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: Asahi Beer Hall | Statement: [Asahi Flame, locatedInTheFacility, Asahi Beer Hall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInTheFacility Context triple: [Asahi Flame, locatedInTheFacility, Asahi Beer Hall]
-
A.
isWithinFacility
chosen
Indicates that one entity is physically located inside the boundaries or premises of a specified facility.
-
B.
partOfFacility
Indicates that one entity is a component, section, or sub-unit belonging to a larger facility.
-
C.
hostedAtFacility
Indicates that an event, activity, or service takes place or is conducted at a specific facility or venue.
-
D.
locatedInBuildingWithFeature
Indicates that something is located in a building that possesses a specified feature or characteristic.
-
E.
basedOnFacility
Indicates that something is determined, derived, or decided according to the characteristics, rules, or conditions of a particular facility.
- F. None of above.
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_69f349177ddc8190ab0583f05597056b |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a02fb5ca96081908ff618f560011940 |
completed | May 12, 2026, 10:05 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a33e8b9c2f08190b77561680aff02d9 |
completed | June 18, 2026, 12:46 p.m. |
| PD | Predicate disambiguation | batch_6a02f9602b308190a97f81821e12b13f |
completed | May 12, 2026, 9:56 a.m. |
Created at: May 1, 2026, 12:51 a.m.