Triple
T31173040
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | David Swan |
E794664
|
entity |
| Predicate | physicalAction |
P171620
|
FINISHED |
| Object | rests in the shade |
—
|
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: rests in the shade | Statement: [David Swan, physicalAction, rests in the shade]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: physicalAction Context triple: [David Swan, physicalAction, rests in the shade]
-
A.
commonAction
Indicates that multiple entities participate in or perform the same action or activity.
-
B.
physicalRequirement
Indicates that one entity specifies a necessary physical condition, capability, or resource that must be met or possessed for another entity, action, or process to occur or be valid.
-
C.
actuatedBy
Indicates that an action, process, or mechanism is initiated, driven, or controlled by a specific agent or cause.
-
D.
formOfAction
Indicates that one action is a specific manner, variant, or implementation of another more general action.
-
E.
forcesAction
Indicates that one entity compels or coerces another entity to perform a specific action or behavior.
- 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_69f224d5b9708190b6ca79ad2fd3a28a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6a1ac56b88190a820434b65c9fa23 |
completed | May 3, 2026, 1:15 a.m. |
| PD | Predicate disambiguation | batch_69f69fe463248190aa78128abeab1183 |
completed | May 3, 2026, 1:07 a.m. |
| PDg | Predicate description generation | batch_69f6a0e920cc8190a943fdd0594906c5 |
completed | May 3, 2026, 1:12 a.m. |
Created at: April 29, 2026, 9:07 p.m.