Triple
T5513647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Infocom |
E144627
|
entity |
| Predicate | cornerstoneImpact |
P51728
|
FINISHED |
| Object | financial difficulties |
—
|
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: financial difficulties | Statement: [Infocom, cornerstoneImpact, financial difficulties]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cornerstoneImpact Context triple: [Infocom, cornerstoneImpact, financial difficulties]
-
A.
cornerstoneLaidBy
Indicates that the act of laying a building’s cornerstone was performed by a specified agent or entity.
-
B.
recognizesImpactOn
Indicates that one entity acknowledges or understands the effect or consequences it has on another entity or situation.
-
C.
impactCategory
chosen
Indicates the type or domain of effect that one entity or action has on another, classifying the nature of its impact.
-
D.
claimsFoundationBy
Indicates that one entity asserts or declares that another entity serves as its basis, origin, or underlying foundation.
-
E.
impactOrigin
Indicates that one entity is the source or cause from which the impact or effect on another entity originates.
- 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_69c008f77ff88190b0cd50ca207295d1 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01f599d0881909ce86fcc45d4d920 |
completed | March 22, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69c01b07bde08190b3933b96bdc70dd5 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:33 p.m.