Triple
T2929099
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Highlands region |
E78915
|
entity |
| Predicate | developmentIssue |
P13650
|
FINISHED |
| Object | limited infrastructure |
—
|
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: limited infrastructure | Statement: [Highlands region, developmentIssue, limited infrastructure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developmentIssue Context triple: [Highlands region, developmentIssue, limited infrastructure]
-
A.
knownIssue
Indicates that the subject has an issue or problem that is already identified, recognized, or documented.
-
B.
developmentFunction
Indicates a relationship where one entity serves as a function, role, or mechanism that drives, supports, or shapes the development or growth of another entity.
-
C.
development
Indicates a process or relationship in which something grows, advances, or becomes more complex or mature over time.
-
D.
platformIssue
Indicates that there is a problem, malfunction, or limitation affecting the operation or availability of a platform.
-
E.
facingIssue
chosen
Indicates that an entity is currently experiencing, encountering, or dealing with a problem, difficulty, or obstacle.
- 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_69ad8b0d40b481908bc2a5fa2e73c3fb |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad98002da4819098d6448eebcafad4 |
completed | March 8, 2026, 3:38 p.m. |
| PD | Predicate disambiguation | batch_69ad9606e8348190bb19df33a2709674 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:55 p.m.