Triple
T9468556
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JetBlue TrueBlue |
E228333
|
entity |
| Predicate | hasEnrollmentCost |
P73251
|
FINISHED |
| Object | free to join |
—
|
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: free to join | Statement: [JetBlue TrueBlue, hasEnrollmentCost, free to join]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEnrollmentCost Context triple: [JetBlue TrueBlue, hasEnrollmentCost, free to join]
-
A.
hasCost
chosen
Indicates that one entity requires a specified amount of resources (such as money, time, or effort) to be obtained, used, or maintained by another entity.
-
B.
usesEnrollment
Indicates that one entity employs or relies on a particular enrollment record, process, or status in order to function or be applied.
-
C.
hasStudentEnrollment
Indicates that a person or entity is enrolled as a student in a particular course, program, or educational institution.
-
D.
isTuitionFreeFor
Indicates that one entity does not require another entity to pay tuition fees for access, enrollment, or participation.
-
E.
enrolledIn
Indicates that one entity is formally registered as a participant in a course, program, or institution represented by another entity.
- 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_69ca846fee388190a6ec273fd644b88b |
completed | March 30, 2026, 2:10 p.m. |
| NER | Named-entity recognition | batch_69cd7fdf604481909bf7d7d477230ca3 |
completed | April 1, 2026, 8:28 p.m. |
| PD | Predicate disambiguation | batch_69cca55f01b081908dc0f12eaa45f832 |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:53 p.m.