Triple
T474301
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Jo |
E9026
|
entity |
| Predicate | colloquialRegister |
P5203
|
FINISHED |
| Object | informal |
—
|
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: informal | Statement: [San Jo, colloquialRegister, informal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: colloquialRegister Context triple: [San Jo, colloquialRegister, informal]
-
A.
isColloquialTerm
Indicates that one term is an informal or non-standard, colloquial way of referring to another term or concept.
-
B.
hasColloquialVariety
chosen
Indicates that one linguistic form, expression, or variety is an informal, colloquial counterpart or version of another.
-
C.
regionalDialect
Indicates that one entity uses or is associated with a dialect specific to a particular geographic region in relation to another entity.
-
D.
spokenForm
Indicates the way something is pronounced or expressed in spoken language, as opposed to its written or symbolic form.
-
E.
ally
Indicates a cooperative relationship in which one entity supports, assists, or aligns with another, often for mutual benefit or a shared goal.
- 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_69a2e7ff81708190b0507a24a997232c |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2f039f3d88190a7c93ecbf1bf5f58 |
completed | Feb. 28, 2026, 1:40 p.m. |
| PD | Predicate disambiguation | batch_69a2edeed31881908cf43beed410572d |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.