Triple
T35305087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ted Caldwell |
E1019613
|
entity |
| Predicate | hasExpectationOf |
P128116
|
FINISHED |
| Object | Harper Caldwell |
—
|
NE NERFINISHED |
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: Harper Caldwell | Statement: [Ted Caldwell, hasExpectationOf, Harper Caldwell]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasExpectationOf Context triple: [Ted Caldwell, hasExpectationOf, Harper Caldwell]
-
A.
setsExpectationsFor
Indicates that one entity defines or communicates standards, requirements, or anticipated outcomes that another entity is expected to meet or follow.
-
B.
holderExpectation
chosen
Indicates that one entity has an expectation, belief, or anticipated outcome regarding another entity or situation.
-
C.
hasStabilityExpectation
Indicates that one entity expects another entity to maintain a certain level or condition of stability over time.
-
D.
expectsEvent
Indicates that one entity anticipates, awaits, or is scheduled to receive the occurrence of a specific event.
-
E.
hasTemporalExpectation
Indicates that one entity holds an expectation about when (in time) another event, state, or action will occur or be valid.
- 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_69f76de8b4c48190ae504b86185c474c |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fd32848ea88190a71e6df402bbb30e |
completed | May 8, 2026, 12:47 a.m. |
| PD | Predicate disambiguation | batch_69fd2d7e95588190991d5f21e25155df |
completed | May 8, 2026, 12:25 a.m. |
Created at: May 3, 2026, 4:03 p.m.