Triple
T30390357
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Winnie Foster |
E773063
|
entity |
| Predicate | facesDecisionAbout |
P2273
|
FINISHED |
| Object | drinking from the spring |
—
|
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: drinking from the spring | Statement: [Winnie Foster, facesDecisionAbout, drinking from the spring]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: facesDecisionAbout Context triple: [Winnie Foster, facesDecisionAbout, drinking from the spring]
-
A.
decisionsAre
Indicates that certain choices, judgments, or resolutions possess a specified quality, status, or classification.
-
B.
decisiveFor
Indicates that one entity plays a determining or conclusive role in bringing about a particular outcome, decision, or state of another entity.
-
C.
decidesOn
chosen
Indicates that an agent makes a choice or determination regarding a particular option, issue, or course of action.
-
D.
knownForDecision
Indicates that an entity is recognized or notable specifically for making a particular decision.
-
E.
decisionType
Indicates the specific category or nature of a decision associated with an entity or event.
- 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_69f2248ef0a48190aa54d4d8ac3e5758 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6859bbd7c81909084682a99f2b9be |
completed | May 2, 2026, 11:15 p.m. |
| PD | Predicate disambiguation | batch_69f678d019fc8190913662cd2f87b857 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 8:02 p.m.