Triple
T36448694
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | StudyLink |
E897946
|
entity |
| Predicate | dataSharingWith |
P77966
|
FINISHED |
| Object | Inland Revenue for loan management |
—
|
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: Inland Revenue for loan management | Statement: [StudyLink, dataSharingWith, Inland Revenue for loan management]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataSharingWith Context triple: [StudyLink, dataSharingWith, Inland Revenue for loan management]
-
A.
dataSharingModel
Indicates a relationship where one entity defines or uses a structured approach or framework for how data is shared between parties.
-
B.
dataSharedWith
chosen
Indicates that some data has been disclosed or made accessible by one entity to another entity.
-
C.
sharesDamWith
Indicates that two entities are impounded or regulated by the same dam structure.
-
D.
sharesUniverseWith
Indicates that two entities exist within the same fictional or narrative universe, implying shared continuity, setting, or canon.
-
E.
dataDistributedTo
Indicates that data has been delivered or made available from one entity to one or more other entities.
- 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_69f76e5720b481908f8177ac24a7560b |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bccf05bc8190b61fdb2b2a315811 |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:10 p.m.