Triple
T6945193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Borssum |
E160778
|
entity |
| Predicate | hasLocalInfrastructure |
P2560
|
FINISHED |
| Object | schools |
—
|
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: schools | Statement: [Borssum, hasLocalInfrastructure, schools]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLocalInfrastructure Context triple: [Borssum, hasLocalInfrastructure, schools]
-
A.
hasGlobalInfrastructure
Indicates that an entity possesses infrastructure, facilities, or operational capabilities that are distributed across multiple countries or regions worldwide.
-
B.
usesInfrastructure
Indicates that one entity makes use of, depends on, or operates through the infrastructure provided or managed by another entity.
-
C.
hasInfrastructureType
chosen
Indicates that an entity possesses or is associated with a specific category or type of infrastructure.
-
D.
hasInfrastructureOwner
Indicates that one entity owns or is responsible for the infrastructure associated with another entity.
-
E.
hasInfrastructureScale
Indicates the relative size, capacity, or extent of infrastructure associated with or supporting an entity.
- 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_69c68850419081909fb426b8f5a304c7 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6e0c74fe48190aeaa018631e52ef6 |
completed | March 27, 2026, 7:55 p.m. |
| PD | Predicate disambiguation | batch_69c6d7bd5a388190a57a96d925696ff6 |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:28 p.m.