Triple
T7153152
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Executive Club |
E166741
|
entity |
| Predicate | benefitForStatus |
P55857
|
FINISHED |
| Object | priority check-in |
—
|
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: priority check-in | Statement: [Executive Club, benefitForStatus, priority check-in]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: benefitForStatus Context triple: [Executive Club, benefitForStatus, priority check-in]
-
A.
benefitsState
Indicates that one entity provides an advantage, improvement, or positive outcome to a state or governmental entity.
-
B.
benefitTaxStatus
Indicates that an entity’s tax-related status or classification provides a financial or regulatory benefit in the context of the relationship.
-
C.
benefitsAre
Indicates that certain advantages, gains, or positive outcomes are possessed by or accrue to a particular entity or group.
-
D.
hasBenefit
Indicates that one entity provides an advantage, improvement, or positive outcome to another entity.
-
E.
criterionForBenefits
chosen
Indicates that something serves as a condition or standard that must be met in order for an entity to receive certain benefits.
- 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_69c68886779c8190a8e3fbabffe68253 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e7f52c1081908c4fa424d5e965bc |
completed | March 27, 2026, 8:26 p.m. |
| PD | Predicate disambiguation | batch_69c6e1caf4e48190b47bb398a3c1554d |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:46 p.m.