Triple
T22557442
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apemosyne |
E557724
|
entity |
| Predicate | purposeOfTransfer |
P88040
|
FINISHED |
| Object | to be sold abroad |
—
|
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: to be sold abroad | Statement: [Apemosyne, purposeOfTransfer, to be sold abroad]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: purposeOfTransfer Context triple: [Apemosyne, purposeOfTransfer, to be sold abroad]
-
A.
transferReason
chosen
Indicates the reason or justification for a transfer occurring between entities.
-
B.
relocatedForPurpose
Indicates that an entity moved from one location to another specifically to fulfill or pursue a particular purpose or objective.
-
C.
purposeOfAddress
Indicates the reason or intended use for which a particular address is provided or utilized.
-
D.
transferredUnder
Indicates that something is moved, conveyed, or reassigned from one party, context, or control to another under specified terms or conditions.
-
E.
transferType
Indicates the specific method or category of how 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_69e11e59db848190b4272ecd2b690ffd |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15f7b06e08190b3ca82a783965942 |
completed | April 29, 2026, 1:31 a.m. |
| PD | Predicate disambiguation | batch_69e898cb3fb48190add6ab24a2df5822 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:52 p.m.