Triple
T37432599
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asiana Club miles |
E930181
|
entity |
| Predicate | areTransferable |
P90522
|
FINISHED |
| Object | sometimes |
—
|
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: sometimes | Statement: [Asiana Club miles, areTransferable, sometimes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: areTransferable Context triple: [Asiana Club miles, areTransferable, sometimes]
-
A.
hasTransfer
Indicates a relationship where something is moved or conveyed from one entity or location to another.
-
B.
allowsTransferTo
Indicates that one entity permits or enables the transfer of something (such as rights, funds, or data) to another specified entity.
-
C.
hasTransferOption
Indicates that there exists a way or method for something (e.g., funds, data, ownership, or passengers) to be transferred from one entity or location to another.
-
D.
transferable
chosen
Indicates that a right, property, or obligation can be legally or practically passed from one entity to another.
-
E.
mayBeTransferredIf
Indicates that something is allowed to be transferred from one party or context to another under certain conditions.
- 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_69f76ebfdcb8819098562ff3db673b04 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb92efc5948190a040ba2028bab964 |
completed | May 6, 2026, 7:13 p.m. |
| PD | Predicate disambiguation | batch_69fb8d0b52588190bb29937a43b99b5e |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 3, 2026, 4:17 p.m.