Triple
T14743602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qmiles |
E346410
|
entity |
| Predicate | validityPolicy |
P82112
|
FINISHED |
| Object | subject to expiry after a defined period |
—
|
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: subject to expiry after a defined period | Statement: [Qmiles, validityPolicy, subject to expiry after a defined period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: validityPolicy Context triple: [Qmiles, validityPolicy, subject to expiry after a defined period]
-
A.
validityType
Indicates the specific kind or category of validity that characterizes how or under what conditions something is considered valid.
-
B.
validityRegime
chosen
Indicates the set of conditions, rules, or context under which something (such as a statement, document, or status) is considered valid or in force.
-
C.
hasValidity
Indicates that something possesses a period or condition during which it is considered legally, logically, or functionally acceptable or in force.
-
D.
establishedPolicy
Indicates that a policy has been formally created, adopted, and put into effect as a guiding rule or standard.
-
E.
hasValidityPeriod
Indicates that something is associated with a specific time span during which it is considered valid or in effect.
- 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_69d822e6f1c88190bc494d491a907114 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dec7367a1c819081082cc355e385fa |
completed | April 14, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69de8bf9331481909582045cd567d91f |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:30 a.m.