Triple
T19596809
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hindu Council UK |
E470367
|
entity |
| Predicate | umbrellaFor |
P95525
|
FINISHED |
| Object | local Hindu organizations in the United Kingdom |
—
|
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 Hindu organizations in the United Kingdom | Statement: [Hindu Council UK, umbrellaFor, local Hindu organizations in the United Kingdom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: umbrellaFor Context triple: [Hindu Council UK, umbrellaFor, local Hindu organizations in the United Kingdom]
-
A.
hasUmbrellas
Indicates that one entity possesses, contains, or is associated with one or more umbrellas.
-
B.
hasUmbrella
Indicates that one entity possesses or is carrying an umbrella.
-
C.
hasUmbrellaBody
Indicates that one entity possesses or is equipped with an umbrella as part of its body or physical form.
-
D.
brandUmbrella
chosen
Indicates that one brand functions as an overarching or parent brand under which another brand is grouped or marketed.
-
E.
airCover
Indicates the provision of protective support from the air (such as aircraft or aerial defenses) to shield or assist another force, operation, or asset.
- 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_69d8e510024481908415c0d616fa6186 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e6407b997881909762c8f919c9cdad |
completed | April 20, 2026, 3:04 p.m. |
| PD | Predicate disambiguation | batch_69e514e166dc8190a0f147e0b4c8bbe7 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:43 p.m.