Triple
T22062855
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BSF |
E545194
|
entity |
| Predicate | locatedInNetworkDomain |
P66218
|
FINISHED |
| Object | home 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: home network | Statement: [BSF, locatedInNetworkDomain, home network]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInNetworkDomain Context triple: [BSF, locatedInNetworkDomain, home network]
-
A.
inNetwork
chosen
Indicates that one entity is within the same defined network, system, or coverage group as another entity, such that network-based interactions or benefits apply between them.
-
B.
isPartOfNetworkManagedBy
Indicates that an entity belongs to and operates under the control or administration of a specific network management authority or system.
-
C.
containsDomain
Indicates that one entity includes or encompasses a specific domain as part of its scope, structure, or area of applicability.
-
D.
usedInDomain
Indicates that something (such as a concept, method, or resource) is applied or utilized within a particular domain or field.
-
E.
locatedInOrganizationally
Indicates that one entity is organizationally situated within, or belongs to, another entity in terms of administrative or structural hierarchy.
- 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_69e11e3377c48190890c17407b9527d6 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f1285e8c688190b701e417893cc148 |
completed | April 28, 2026, 9:36 p.m. |
| PD | Predicate disambiguation | batch_69e6f643ca74819083e8ab78e843f243 |
completed | April 21, 2026, 4 a.m. |
Created at: April 16, 2026, 8:27 p.m.