Triple
T1407738
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Drunken Clam regulars |
E31732
|
entity |
| Predicate | typicalSceneType |
P4566
|
FINISHED |
| Object | bar conversation scenes |
—
|
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: bar conversation scenes | Statement: [The Drunken Clam regulars, typicalSceneType, bar conversation scenes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalSceneType Context triple: [The Drunken Clam regulars, typicalSceneType, bar conversation scenes]
-
A.
typicalGameLocation
Indicates the usual or characteristic place where a game is played or takes place.
-
B.
typicalBackground
chosen
Indicates that an entity has a usual or commonly expected background, context, or setting associated with it.
-
C.
performedInSceneType
Indicates that an action or event was carried out within a scene of a specified type or category.
-
D.
typicalVenues
Indicates that the specified locations are common or standard places where the associated activity, event, or entity usually occurs or is hosted.
-
E.
placeOfSetting
Indicates the location or environment where an event, scene, or situation takes place.
- 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_69a49918e1f88190ba610f9dc8114578 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c3bf7f0c8190aee96818de6ff4a5 |
completed | March 1, 2026, 10:54 p.m. |
| PD | Predicate disambiguation | batch_69a4bf030a388190bc82d30b9233e873 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:59 p.m.