Triple
T17378915
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Waitstill |
E422513
|
entity |
| Predicate | frequencyInModernUse |
P3657
|
FINISHED |
| Object | very low |
—
|
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: very low | Statement: [Waitstill, frequencyInModernUse, very low]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: frequencyInModernUse Context triple: [Waitstill, frequencyInModernUse, very low]
-
A.
contemporaryUse
Indicates that something is currently used or practiced in the present time or modern context.
-
B.
frequencyInHistory
Indicates how often a particular event, state, or relationship has occurred over time within a given historical context.
-
C.
emergedInModernForm
Indicates that something developed into or appeared in its current recognizable form during the modern era.
-
D.
modernUse
chosen
Indicates how something is currently used or applied in modern times.
-
E.
modernUsageContext
Indicates the contemporary or current context in which something is used, applied, or functions.
- 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_69d889d6535c81908be333c01deaec4e |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a840cd08190af3385388afb8c8f |
completed | April 19, 2026, 2:14 a.m. |
| PD | Predicate disambiguation | batch_69e3b02ac8688190a7182f1b2151d721 |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:45 a.m.