Triple
T29968772
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interpol Information System |
E761260
|
entity |
| Predicate | dataSharingModel |
P168306
|
FINISHED |
| Object | information shared by member countries |
—
|
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: information shared by member countries | Statement: [Interpol Information System, dataSharingModel, information shared by member countries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataSharingModel Context triple: [Interpol Information System, dataSharingModel, information shared by member countries]
-
A.
sharesAcademicModelWith
Indicates that two entities use or are based on the same academic framework, structure, or model.
-
B.
dataModel
Indicates a relationship where an entity defines, uses, or is structured according to a specific data model or schema.
-
C.
dataSharedWith
Indicates that some data has been disclosed or made accessible by one entity to another entity.
-
D.
dataDistributedTo
Indicates that data has been delivered or made available from one entity to one or more other entities.
-
E.
dataAccessibleTo
Indicates that certain data can be reached, retrieved, or used by a specified entity or system.
- F. None of above. chosen
Provenance (4 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_69f22467626081908d5afea489590e96 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6786c984c8190b7668a6232901b30 |
completed | May 2, 2026, 10:19 p.m. |
| PD | Predicate disambiguation | batch_69f66ec8298c8190b41fe9d182c05676 |
completed | May 2, 2026, 9:38 p.m. |
| PDg | Predicate description generation | batch_69f67256d064819094be04fc1bbbc635 |
completed | May 2, 2026, 9:53 p.m. |
Created at: April 29, 2026, 6:31 p.m.