Triple
T11238055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LifeMiles |
E265994
|
entity |
| Predicate | milesCanBeTransferred |
P59707
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [LifeMiles, milesCanBeTransferred, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: milesCanBeTransferred Context triple: [LifeMiles, milesCanBeTransferred, true]
-
A.
vehicleRestrictionMile
Indicates a restriction or limitation that applies to vehicles at a specific mile point or mile marker along a route.
-
B.
mayBeTransferredIf
chosen
Indicates that something is allowed to be transferred from one party or context to another under certain conditions.
-
C.
mileageAccrual
Indicates the accumulation or earning of mileage (such as distance-based points or credits) as a result of certain actions or usage.
-
D.
approximateLengthInMiles
Indicates the estimated distance or extent of something measured in miles.
-
E.
hasTransferOption
Indicates that there exists a way or method for something (e.g., funds, data, ownership, or passengers) to be transferred from one entity or location to another.
- 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_69d6aac656d48190b275efaa7d6074ee |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e918375081908c2a7ccb50cbf331 |
completed | April 9, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69d7878906f48190b63ddc103a0c8f9b |
completed | April 9, 2026, 11:03 a.m. |
Created at: April 8, 2026, 9:30 p.m.