Triple
T31223897
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Global Britain |
E796085
|
entity |
| Predicate | developmentDimension |
P47059
|
FINISHED |
| Object | development assistance |
—
|
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: development assistance | Statement: [Global Britain, developmentDimension, development assistance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developmentDimension Context triple: [Global Britain, developmentDimension, development assistance]
-
A.
hasDevelopmentDimension
chosen
Indicates that something possesses or is associated with a particular aspect or dimension of development.
-
B.
development
Indicates a process or relationship in which something grows, advances, or becomes more complex or mature over time.
-
C.
developmentLinkedTo
Indicates that the development or progression of one entity is causally or contextually connected to the development or progression of another entity.
-
D.
developmentDirection
Indicates the primary orientation or path along which something grows, progresses, or evolves over time.
-
E.
developmentFor
Indicates that one entity is created, adapted, or advanced specifically for the benefit, use, or purpose of another 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_69f224da98f88190ab32f690cce5d303 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f78c61ed4c8190ad84c918fa9af55a |
completed | May 3, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69f78b8cb3a881909ebaac1b503988c2 |
completed | May 3, 2026, 5:53 p.m. |
Created at: April 29, 2026, 9:10 p.m.