Triple
T34448061
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Countess Cathleen |
E884282
|
entity |
| Predicate | purposeOfOffer |
P178952
|
FINISHED |
| Object | to save her famine‑stricken people |
—
|
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: to save her famine‑stricken people | Statement: [Countess Cathleen, purposeOfOffer, to save her famine‑stricken people]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: purposeOfOffer Context triple: [Countess Cathleen, purposeOfOffer, to save her famine‑stricken people]
-
A.
offeringType
Indicates the category or nature of what is being offered in a transaction or interaction (e.g., product, service, or other type of offering).
-
B.
offering
Indicates that one entity presents or provides something to another entity, typically as a gift, contribution, or proposal.
-
C.
purposeOfDeclaration
Indicates that a declaration is made with the specific aim, goal, or intended function of the associated entity or action.
-
D.
conditionOfOffer
Indicates the terms, requirements, or circumstances under which an offer is valid or applies.
-
E.
offersInformationOn
Indicates that one entity provides or makes available information about another entity or topic.
- 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_69f349c607688190b553539d14901a35 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f719cc31ec819099bebcf833b14d76 |
completed | May 3, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69f71824431081908d9685d2462ea242 |
completed | May 3, 2026, 9:40 a.m. |
| PDg | Predicate description generation | batch_69f719458378819081725f544efb1173 |
completed | May 3, 2026, 9:45 a.m. |
Created at: May 1, 2026, 2 a.m.