Triple
T29084457
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paul Jesperson |
E734065
|
entity |
| Predicate | transferStatus |
P44956
|
FINISHED |
| Object | transferred from Virginia to Northern Iowa |
—
|
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: transferred from Virginia to Northern Iowa | Statement: [Paul Jesperson, transferStatus, transferred from Virginia to Northern Iowa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transferStatus Context triple: [Paul Jesperson, transferStatus, transferred from Virginia to Northern Iowa]
-
A.
transferType
Indicates the specific method or category of how something is transferred from one entity to another.
-
B.
transferAfter
Indicates that one entity transfers something to another entity only after a specified event or condition has occurred.
-
C.
transferEvent
chosen
Indicates an event in which something is moved, handed over, or reassigned from one entity to another.
-
D.
transferMode
Indicates the method or mechanism by which something is transferred from one entity to another.
-
E.
statusTransmission
Indicates that a status or state is being communicated or passed from one entity to another.
- 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_69f05b0c0f28819086eae6e84f2ae472 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69fd4d1854988190be093b103a681798 |
completed | May 8, 2026, 2:40 a.m. |
| PD | Predicate disambiguation | batch_69fd4c8d1a188190897c24527337814a |
completed | May 8, 2026, 2:38 a.m. |
Created at: April 28, 2026, 10:58 a.m.