Triple
T17381923
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flying Club miles |
E422588
|
entity |
| Predicate | subjectToProgramRules |
P119836
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Flying Club miles, subjectToProgramRules, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subjectToProgramRules Context triple: [Flying Club miles, subjectToProgramRules, yes]
-
A.
authorizedUnderProgram
chosen
Indicates that an entity’s action, status, or participation is permitted or governed according to the rules or provisions of a specific program.
-
B.
regulatesUnderProgram
Indicates that one entity exercises regulatory authority or control over another entity within the scope of a specific program or regulatory scheme.
-
C.
underRule
Indicates that one entity is governed, controlled, or subject to the authority, rules, or dominion of another entity.
-
D.
eligibilityRulesSetBy
Indicates that one party defines or establishes the criteria or rules determining another party’s eligibility for something.
-
E.
regulatesProgram
Indicates that one entity exercises control or governance over the operation, rules, or functioning of a program.
- 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_69d889d6535c81908be333c01deaec4e |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a86d8cc81909281b22f5da87d70 |
completed | April 19, 2026, 2:14 a.m. |
| PD | Predicate disambiguation | batch_69e3b02ac8688190a7182f1b2151d721 |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:45 a.m.