Triple
T9241432
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mabuhay Miles |
E222066
|
entity |
| Predicate | hasMobileAccess |
P48291
|
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: [Mabuhay Miles, hasMobileAccess, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMobileAccess Context triple: [Mabuhay Miles, hasMobileAccess, yes]
-
A.
hasDigitalAccess
Indicates that an entity has the ability or permission to use or access digital resources, services, or information.
-
B.
allowsMobileReception
chosen
Indicates that one entity provides the conditions or infrastructure necessary for another entity to receive mobile (cellular) network service.
-
C.
hasCellularComponent
Indicates that an entity possesses, includes, or is associated with a specific cellular component as part of its structure or organization.
-
D.
hasMob
Indicates that an entity possesses, controls, or is associated with a particular mob or group of mobile agents.
-
E.
hasBridgeAccess
Indicates that an entity is permitted to enter or use a specific bridge or bridge-controlled area.
- 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_69ca83ee26cc81909ac624e190597d6d |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cd03ea9d90819096f9ca5321dffd56 |
completed | April 1, 2026, 11:39 a.m. |
| PD | Predicate disambiguation | batch_69cc7a4765648190aa9445c4a22dc471 |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:30 p.m.