Triple
T5229101
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | White British |
E118063
|
entity |
| Predicate | dataCollectedFor |
P4241
|
FINISHED |
| Object | equality monitoring |
—
|
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: equality monitoring | Statement: [White British, dataCollectedFor, equality monitoring]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataCollectedFor Context triple: [White British, dataCollectedFor, equality monitoring]
-
A.
dataTypeCollected
chosen
Indicates that a specific type or category of data is gathered or recorded in the context of an entity or process.
-
B.
collectedThrough
Indicates that something was obtained, gathered, or acquired by means of a specified process, method, or channel.
-
C.
collectsInformationOn
Indicates that one entity gathers or acquires data, facts, or details about another entity.
-
D.
dataPortal
Indicates that an entity serves as or is associated with an online interface or gateway through which data can be accessed, managed, or distributed.
-
E.
dataSubject
Indicates that one entity is the individual to whom the personal data or information in question relates.
- 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_69bd4466fb8c819083b806a79414d7e4 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7b0093a88190aba381ba3f761408 |
completed | March 20, 2026, 4:51 p.m. |
| PD | Predicate disambiguation | batch_69bd77bf1ef08190bb3487b3f3ee088c |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:48 p.m.