Triple
T38212402
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parikrama (circumambulatory path) |
E1010583
|
entity |
| Predicate | hasEtiquette |
P193399
|
FINISHED |
| Object | no smoking |
—
|
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: no smoking | Statement: [Parikrama (circumambulatory path), hasEtiquette, no smoking]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEtiquette Context triple: [Parikrama (circumambulatory path), hasEtiquette, no smoking]
-
A.
hasManner
Indicates the way, style, or method in which an action is performed or a relation is carried out.
-
B.
requiresStandingEtiquette
Indicates that the situation or action necessitates following proper etiquette or manners specifically while standing.
-
C.
hasPolitenessSystem
Indicates that a language or communication system includes formalized ways of expressing different levels of politeness or social hierarchy.
-
D.
hasPolitePronoun
Indicates that one entity refers to another using a polite or honorific form of address in language.
-
E.
drinkingEtiquette
Indicates the socially appropriate behaviors, norms, and rules governing how one should drink in a given context.
- 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_69f76dcdc7708190a5f1751d53f40ffe |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fd44474ed48190ac372e4c88d762ed |
completed | May 8, 2026, 2:02 a.m. |
| PD | Predicate disambiguation | batch_69fd41ef28a48190a66959be5c964461 |
completed | May 8, 2026, 1:52 a.m. |
| PDg | Predicate description generation | batch_69fd4445f8c08190bb2dc27e0971c55d |
completed | May 8, 2026, 2:02 a.m. |
Created at: May 3, 2026, 4:30 p.m.