Triple
T27646007
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BOCs |
E696713
|
entity |
| Predicate | own |
P132765
|
FINISHED |
| Object | local loop infrastructure in their regions |
—
|
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: local loop infrastructure in their regions | Statement: [BOCs, own, local loop infrastructure in their regions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: own Context triple: [BOCs, own, local loop infrastructure in their regions]
-
A.
ownedMostOf
Indicates that one entity possessed the majority share or largest portion of another entity or resource, relative to all other owners.
-
B.
privateOwnership
chosen
Indicates that a specified entity holds legal ownership or control over something in a private, non-public capacity.
-
C.
ownedIn
Indicates that one entity possesses or holds legal or recognized ownership of another entity within a specific context, domain, or scope.
-
D.
ownedThrough
Indicates that one entity possesses or controls another indirectly via an intermediate entity, structure, or arrangement (such as a subsidiary, trust, or other vehicle).
-
E.
ownedProperty
Indicates that one entity possesses legal ownership or control over another entity as property.
- 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_69ef590abd3c8190834d0193bde12007 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f63195d7808190a4d4bde80e99d31d |
completed | May 2, 2026, 5:17 p.m. |
| PD | Predicate disambiguation | batch_69f62c1921008190a62675a31f66a875 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 2:29 p.m.