Triple
T31173046
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | David Swan |
E794664
|
entity |
| Predicate | awarenessAtEnd |
P151290
|
FINISHED |
| Object | believes nothing remarkable has happened |
—
|
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: believes nothing remarkable has happened | Statement: [David Swan, awarenessAtEnd, believes nothing remarkable has happened]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: awarenessAtEnd Context triple: [David Swan, awarenessAtEnd, believes nothing remarkable has happened]
-
A.
knowledgeStatusAtEnd
chosen
Indicates the final state or outcome of an entity’s knowledge after a process, event, or time period has concluded.
-
B.
isUsuallyTakenAtEndOf
Indicates that one event, action, or item typically occurs or is taken after the completion of another.
-
C.
endOfActivity
Indicates that a particular activity has reached its completion or final point in time.
-
D.
statusEndsWhen
Indicates that a particular status or condition ceases to hold when a specified event, time, or state occurs.
-
E.
endOf
Indicates that one entity marks the terminating point or final boundary of another entity, event, or interval.
- 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_69f224d5b9708190b6ca79ad2fd3a28a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69c234d648190a243fb2b107136a9 |
completed | May 3, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69f69665cd9c819088c388fc82fec42e |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 9:07 p.m.