Triple
T9422316
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Koiak |
E227182
|
entity |
| Predicate | notablePractices |
P12146
|
FINISHED |
| Object | midnight praises |
—
|
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: midnight praises | Statement: [Koiak, notablePractices, midnight praises]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notablePractices Context triple: [Koiak, notablePractices, midnight praises]
-
A.
currentBestPractice
Indicates that something represents the most up-to-date and widely accepted recommended method or standard at the present time.
-
B.
notableStandard
Indicates that one entity is a widely recognized or influential standard that the other entity is associated with or exemplifies.
-
C.
notableGuideline
Indicates that something is recognized as an important or especially significant rule, principle, or recommended practice.
-
D.
recommendedPracticeDefinition
Indicates that one entity defines or specifies the content or meaning of a recommended practice associated with another entity.
-
E.
typicalPractice
chosen
Indicates that an action, behavior, or method is commonly or customarily done in a given context or by a given group.
- 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_69ca8436ba308190903e470776d2d893 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd6c2651c48190808281779fab49df |
completed | April 1, 2026, 7:04 p.m. |
| PD | Predicate disambiguation | batch_69cca550777c819094e1851a6127cbbc |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:48 p.m.