Triple
T14604956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charlie West |
E342804
|
entity |
| Predicate | colloquialUsage |
P29199
|
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: [Charlie West, colloquialUsage, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: colloquialUsage Context triple: [Charlie West, colloquialUsage, yes]
-
A.
isColloquialTerm
Indicates that one term is an informal or non-standard, colloquial way of referring to another term or concept.
-
B.
typicalLanguageUse
Indicates that one entity is the language most commonly or habitually used by another entity in ordinary communication or contexts.
-
C.
linguisticUsage
chosen
Indicates how a linguistic form, expression, or construction is used in language, such as its typical context, function, or register.
-
D.
usesSlangFrom
Indicates that one entity incorporates or employs slang expressions originating from another entity or source.
-
E.
hasColloquialVariety
Indicates that one linguistic form, expression, or variety is an informal, colloquial counterpart or version of another.
- 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_69d822dec68081908c2553145c4051dc |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb44bf67c8190b4c48a7715f9443e |
completed | April 14, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69de656f9f4c81909f815b6629a9ee39 |
completed | April 14, 2026, 4:03 p.m. |
Created at: April 10, 2026, 1:25 a.m.