Triple
T12317305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hills Like White Elephants |
E293633
|
entity |
| Predicate | impliedTopic |
P12980
|
FINISHED |
| Object | abortion |
—
|
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: abortion | Statement: [Hills Like White Elephants, impliedTopic, abortion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: impliedTopic Context triple: [Hills Like White Elephants, impliedTopic, abortion]
-
A.
subjectImpliedAs
Indicates that the subject of an action or statement is not explicitly stated but is understood or inferred from context.
-
B.
primaryTopicOf
chosen
Indicates that a given subject is the main or central topic described by another resource (such as a document, page, or record).
-
C.
coveredTopics
Indicates that certain subjects or themes have been addressed or included within a discussion, document, or activity.
-
D.
impliedCreation
Indicates that one entity is understood to have brought another entity into existence, even if the act of creation is not explicitly stated.
-
E.
impliedRight
Indicates that one party holds a right or entitlement that is not explicitly stated but is inferred from context, agreements, or established norms.
- 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_69d6ab6a2b50819082f6aedd32ed608a |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d93f621570819091ee1db2609233ea |
completed | April 10, 2026, 6:20 p.m. |
| PD | Predicate disambiguation | batch_69d93ec5be788190b82d2edc6a0f1095 |
completed | April 10, 2026, 6:17 p.m. |
Created at: April 8, 2026, 9:53 p.m.