Triple
T25832865
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bung |
E650711
|
entity |
| Predicate | socialRegister |
P33136
|
FINISHED |
| Object | colloquial |
—
|
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: colloquial | Statement: [Bung, socialRegister, colloquial]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: socialRegister Context triple: [Bung, socialRegister, colloquial]
-
A.
register
Indicates that an entity formally records or enrolls another entity or itself in an official system, list, or record.
-
B.
registrationExample
Indicates that an instance serves as an illustrative or sample case of a particular registration.
-
C.
registrationModel
Indicates the model, schema, or structure used to define how registrations are represented, processed, or stored in the system.
-
D.
socialCustom
chosen
Indicates a culturally shared, customary way of behaving or interacting that is expected or considered appropriate within a particular social group or context.
-
E.
inscriptionMode
Indicates the method or technique by which an inscription is created, applied, or recorded on a surface or medium.
- 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_69e7ab37438081908f1ccf6284839520 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f627aedf548190bc9f53c8a2d67b50 |
completed | May 2, 2026, 4:34 p.m. |
| PD | Predicate disambiguation | batch_69f623a4e1048190bbb8dd1253fdcee9 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 22, 2026, 7:39 a.m.