Triple
T27794298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Labone |
E701163
|
entity |
| Predicate | hasUtilityAccess |
P1017
|
FINISHED |
| Object | mobile telecommunications networks |
—
|
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: mobile telecommunications networks | Statement: [Labone, hasUtilityAccess, mobile telecommunications networks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUtilityAccess Context triple: [Labone, hasUtilityAccess, mobile telecommunications networks]
-
A.
hasHumanAccess
Indicates that a human is able to access, use, or interact with the referenced entity or resource.
-
B.
hasAccessTo
chosen
Indicates that one entity is permitted to enter, use, or interact with another entity, resource, or location.
-
C.
hasAccessTowards
Indicates that one entity possesses the ability, permission, or means to reach, use, or interact with another entity or resource.
-
D.
hasDisabledAccess
Indicates that an entity provides facilities, features, or accommodations that make it accessible to people with disabilities.
-
E.
canAccedeTo
Indicates that one entity has the ability, permission, or right to gain access to or enter into another entity, resource, or state.
- 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_69ef6a50d8088190acbf3dfbb06d8091 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c6895f0819088655277e45859a8 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 5:30 p.m.