Triple
T38028448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spanish Missouri |
E948841
|
entity |
| Predicate | subsequentTransferTo |
P57570
|
FINISHED |
| Object | United States |
—
|
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: United States | Statement: [Spanish Missouri, subsequentTransferTo, United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subsequentTransferTo Context triple: [Spanish Missouri, subsequentTransferTo, United States]
-
A.
transferAfter
Indicates that one entity transfers something to another entity only after a specified event or condition has occurred.
-
B.
allowsTransferTo
Indicates that one entity permits or enables the transfer of something (such as rights, funds, or data) to another specified entity.
-
C.
transferDestination
chosen
Indicates the entity that serves as the receiving end or target location of a transfer from another entity.
-
D.
laterTransmittedAs
Indicates that some information, message, or content was transmitted or communicated at a later time as a particular form, version, or representation.
-
E.
transferMode
Indicates the method or mechanism by which something is transferred 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_69f76efd1bc48190a729097fe5177b61 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc99760d48190a5d0d00c36307456 |
completed | May 6, 2026, 11:07 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ee04f08190977b7ad70fc85896 |
completed | May 6, 2026, 11:04 p.m. |
Created at: May 3, 2026, 4:20 p.m.