Triple
T1543401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wanna Get Away |
E32921
|
entity |
| Predicate | refundForm |
P30184
|
FINISHED |
| Object | travel credit |
—
|
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: travel credit | Statement: [Wanna Get Away, refundForm, travel credit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: refundForm Context triple: [Wanna Get Away, refundForm, travel credit]
-
A.
refundPolicy
Indicates the terms and conditions under which payments are returned or compensated after a purchase or transaction.
-
B.
returnService
Indicates a relationship where a service that was previously provided is being sent back, reversed, or requested to be undone or refunded.
-
C.
rejectedClaim
Indicates that one party has refused to accept, approve, or validate a claim made by another party.
-
D.
releaseForm
Indicates that one entity formally authorizes the release or disclosure of information, rights, or responsibilities to another entity through a consent or waiver document.
-
E.
rejectedOrModifiedBy
Indicates that a proposal, request, or item was either not accepted as-is or was altered by a particular agent or authority.
- 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_69a885ed29088190a3c2d5a3d100c16e |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aa95c1a2948190a2b98469afec1a7d |
completed | March 6, 2026, 8:52 a.m. |
| PD | Predicate disambiguation | batch_69a907b2453c8190a41f6b88c8217d1e |
completed | March 5, 2026, 4:33 a.m. |
| PDg | Predicate description generation | batch_69a93df847cc8190b6d011af33b34b40 |
completed | March 5, 2026, 8:25 a.m. |
Created at: March 4, 2026, 7:26 p.m.