Triple
T37660203
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NBN services |
E937700
|
entity |
| Predicate | providedOver |
P198408
|
FINISHED |
| Object | fixed-line network |
—
|
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: fixed-line network | Statement: [NBN services, providedOver, fixed-line network]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: providedOver Context triple: [NBN services, providedOver, fixed-line network]
-
A.
providedFor
Indicates that one entity supplies, furnishes, or makes something available to or on behalf of another entity for its use or benefit.
-
B.
providedAt
Indicates that something is supplied, made available, or delivered at a specific time or location.
-
C.
providedInformationTo
Indicates that one entity has supplied or communicated information to another entity.
-
D.
providedProduct
Indicates that one entity has supplied or made available a particular product to another entity.
-
E.
laterProvidedFor
Indicates that one entity is supplied, arranged, or made available for another entity at a subsequent time rather than initially.
- F. None of above. chosen
Provenance (4 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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fee0b2da3c8190a3519d0564f2f32d |
completed | May 9, 2026, 7:22 a.m. |
| PD | Predicate disambiguation | batch_69fee05b315c819081dfcbfb15273487 |
completed | May 9, 2026, 7:20 a.m. |
| PDg | Predicate description generation | batch_69fee0b03a0c81909117dc5915d77295 |
completed | May 9, 2026, 7:22 a.m. |
Created at: May 3, 2026, 4:18 p.m.