Triple
T1440386
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Griggs v. Duke Power Co. |
E31055
|
entity |
| Predicate | standardAnnounced |
P29339
|
FINISHED |
| Object | business necessity |
—
|
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: business necessity | Statement: [Griggs v. Duke Power Co., standardAnnounced, business necessity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardAnnounced Context triple: [Griggs v. Duke Power Co., standardAnnounced, business necessity]
-
A.
announcedAs
Indicates that one entity is publicly presented, declared, or introduced in a specified role, name, or capacity by another entity.
-
B.
announcedTo
Indicates that one entity formally communicated or made known some information, decision, or event to another specific entity.
-
C.
announcedThat
Indicates that one entity publicly communicated or declared a specific fact, decision, or piece of information about another entity or situation.
-
D.
announcedAt
Indicates that an announcement or declaration was made at a specific time or event.
-
E.
standardType
Indicates that one entity is classified as the standard, canonical, or reference type for another entity or context.
- F. None of above. chosen
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_69a4991633388190a4d61b5a98aa407a |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c5ff8dbc81909eafcfc9f2260a22 |
completed | March 1, 2026, 11:04 p.m. |
| PD | Predicate disambiguation | batch_69a4c478f65481909ee716791c663491 |
completed | March 1, 2026, 10:58 p.m. |
| PDg | Predicate description generation | batch_69a4c5fd2c5c81909283b7a74aff89b7 |
completed | March 1, 2026, 11:04 p.m. |
Created at: March 1, 2026, 8 p.m.