Triple
T6894370
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GarudaMiles |
E159132
|
entity |
| Predicate | supportsMobileAccess |
P8220
|
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: [GarudaMiles, supportsMobileAccess, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsMobileAccess Context triple: [GarudaMiles, supportsMobileAccess, true]
-
A.
allowsMobileReception
Indicates that one entity provides the conditions or infrastructure necessary for another entity to receive mobile (cellular) network service.
-
B.
hasDigitalAccess
chosen
Indicates that an entity has the ability or permission to use or access digital resources, services, or information.
-
C.
supportsHandheldMode
Indicates that an entity is capable of operating or being used in a handheld mode.
-
D.
mobileVariant
Indicates that one entity is a mobile-specific version or adaptation of another entity.
-
E.
accessModelIntroduced
Indicates that a particular method, mechanism, or pathway for accessing something has been newly introduced or made available.
- 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_69c6883568c8819081db6407e892cccc |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d931da24819096b9b205f2c0ebb0 |
completed | March 27, 2026, 7:23 p.m. |
| PD | Predicate disambiguation | batch_69c6d7b7681481909ec50509b19fcf81 |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:24 p.m.