Triple
T36218203
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yunyarinyi |
E1047760
|
entity |
| Predicate | hasServiceAccessPattern |
P56178
|
FINISHED |
| Object | serviced via regional APY Lands hubs |
—
|
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: serviced via regional APY Lands hubs | Statement: [Yunyarinyi, hasServiceAccessPattern, serviced via regional APY Lands hubs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasServiceAccessPattern Context triple: [Yunyarinyi, hasServiceAccessPattern, serviced via regional APY Lands hubs]
-
A.
hasServicePatternRole
Indicates that an entity participates in a service pattern with a specific functional role or responsibility within that pattern.
-
B.
hasRegularServicePattern
Indicates that an entity consistently follows a defined, recurring schedule or pattern of service over time.
-
C.
hasAccessMethod
chosen
Indicates that one entity uses or is associated with a particular method or mechanism for accessing another entity or resource.
-
D.
hasPeakServicePattern
Indicates that there is a specific service pattern or schedule that applies during peak (busiest) operating periods for the related entity.
-
E.
hasAccessMode
Indicates the type or method of access that one entity is permitted to use with respect to another entity or resource.
- 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_69f76e42c878819095c8d19c0267fb87 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a0049e40d60819081e3899d8d9fca51 |
completed | May 10, 2026, 9:03 a.m. |
| PD | Predicate disambiguation | batch_6a0048c47b548190ad31b2901cc3784a |
completed | May 10, 2026, 8:58 a.m. |
Created at: May 3, 2026, 4:09 p.m.