Triple
T32296347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Louden Swain |
E825109
|
entity |
| Predicate | pushesHimselfTo |
P173938
|
FINISHED |
| Object | extreme lengths |
—
|
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: extreme lengths | Statement: [Louden Swain, pushesHimselfTo, extreme lengths]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pushesHimselfTo Context triple: [Louden Swain, pushesHimselfTo, extreme lengths]
-
A.
overthrustOnto
Indicates that one geological unit has been pushed up and over another along a thrust fault, coming to rest on top of it.
-
B.
turnsHimselfInTo
Indicates that a person voluntarily surrenders or reports himself to an authority, typically law enforcement or another official body.
-
C.
thinksHeIsLeading
Indicates that one entity believes or assumes that he is the one currently leading or in charge in a given situation or activity.
-
D.
calledHimself
Indicates that a person referred to or identified himself using a particular name, title, or description.
-
E.
pushFactor
Indicates a driving influence or pressure that motivates or forces an entity to move away from, leave, or change its current situation or state.
- 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_69f349115304819084ee91d345b6c8aa |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bd3be16081909465eb41815bb768 |
completed | May 3, 2026, 3:13 a.m. |
| PD | Predicate disambiguation | batch_69f6b632cf788190a3d0c08cd026b84b |
completed | May 3, 2026, 2:42 a.m. |
| PDg | Predicate description generation | batch_69f6b960ca4081909a77690c2b122f5e |
completed | May 3, 2026, 2:56 a.m. |
Created at: May 1, 2026, 12:44 a.m.