Triple
T361070
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TrueBlue |
E7852
|
entity |
| Predicate | partnerType |
P282
|
FINISHED |
| Object | airline partners |
—
|
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: airline partners | Statement: [TrueBlue, partnerType, airline partners]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partnerType Context triple: [TrueBlue, partnerType, airline partners]
-
A.
hasPartner
Indicates that one entity is in a partner relationship (such as romantic, life, or business partnership) with another entity.
-
B.
coalitionPartnerWith
Indicates that two entities are formally aligned in a cooperative coalition, sharing goals or actions as partners within that coalition.
-
C.
businessPartner
chosen
Indicates a formal collaborative relationship between two entities that work together in a business context, typically sharing responsibilities, risks, or benefits.
-
D.
expansionPartner
Indicates a relationship where one entity collaborates with another to support or drive its growth into new markets, regions, or domains.
-
E.
participantType
Indicates the specific role or category that a participant has within a given event, activity, or relationship.
- 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_69a2e7e880008190a6ad7e06e5d03007 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ebce64c88190a0a8edcc7095f78b |
completed | Feb. 28, 2026, 1:21 p.m. |
| PD | Predicate disambiguation | batch_69a2e95c843c8190b2aba9af6e869ba1 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.