Triple
T21258998
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guru |
E523945
|
entity |
| Predicate | hasModernUsageContext |
P37480
|
FINISHED |
| Object | informal English |
—
|
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 English | Statement: [Guru, hasModernUsageContext, informal English]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasModernUsageContext Context triple: [Guru, hasModernUsageContext, informal English]
-
A.
includesModernElement
Indicates that something contains or incorporates at least one feature, component, or aspect that is characteristic of the modern era.
-
B.
hasModernSection
Indicates that an entity includes or contains a distinct section devoted to modern or contemporary content, features, or aspects.
-
C.
hasTypicalUseContext
chosen
Indicates that something is commonly or characteristically used within a particular situation, setting, or context.
-
D.
hasModernMisuse
Indicates that something is currently being used in a way that departs from or conflicts with its original, proper, or intended use.
-
E.
hasModernAccessPoint
Indicates that one entity provides or includes a contemporary means or facility through which another entity can be accessed or used.
- 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_69e0b5156d7881909bd4f83676590715 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e735e477d08190be17ad5384d69a80 |
completed | April 21, 2026, 8:31 a.m. |
| PD | Predicate disambiguation | batch_69e5f61239708190ab7b3c83ae848a0d |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3:59 p.m.