Triple
T32774308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stay Lucky |
E838151
|
entity |
| Predicate | typicalDialect |
P1762
|
FINISHED |
| Object | American English |
E2045
|
NE 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: American English | Statement: [Stay Lucky, typicalDialect, American English]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalDialect Context triple: [Stay Lucky, typicalDialect, American English]
-
A.
regionalDialect
chosen
Indicates that one entity uses or is associated with a dialect specific to a particular geographic region in relation to another entity.
-
B.
majorDialectOf
Indicates that one dialect is the primary or most prominent dialect associated with a particular language or region.
-
C.
dominantDialect
Indicates that one dialect is the primary or most influential form of a language within a particular context or region.
-
D.
typicalLanguageUse
Indicates that one entity is the language most commonly or habitually used by another entity in ordinary communication or contexts.
-
E.
notableDialect
Indicates that an entity is recognized for having a distinct or noteworthy dialect associated with it.
- F. None of above.
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_69f3493a824c8190938489ba69041d08 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a34a7bc3e308190a6ee32259cda442b |
completed | June 19, 2026, 2:21 a.m. |
| PD | Predicate disambiguation | batch_6a0379f0cbe481909b4b8fc6cbe297f0 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:13 a.m.