Triple
T35647191
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Delos Destinations |
E1030042
|
entity |
| Predicate | secretPurpose |
P184066
|
FINISHED |
| Object | data harvesting |
—
|
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: data harvesting | Statement: [Delos Destinations, secretPurpose, data harvesting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secretPurpose Context triple: [Delos Destinations, secretPurpose, data harvesting]
-
A.
encodingPurpose
Indicates the reason or intended use for which an encoding is created or applied.
-
B.
accessPurpose
Indicates that one entity uses or accesses another entity specifically for a defined purpose or intended use.
-
C.
entryPurpose
Indicates the reason or intended use for which an entity is being entered, accessed, or recorded in a given context.
-
D.
trustPurpose
Indicates that one entity has a specific intended use, goal, or objective for which a trust or trusted arrangement is established with another entity.
-
E.
maskPurpose
Indicates that one entity serves as the intended purpose, function, or use for which a mask is designed or employed.
- 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_69f76e0938088190a8f199631e97dec3 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aaabb58c8190bf81673608ecfb6e |
completed | May 3, 2026, 8:06 p.m. |
| PD | Predicate disambiguation | batch_69f7a8d219f8819081dc4ce3c83ca0cb |
completed | May 3, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f7aa6795f481908940838ee7041ff5 |
completed | May 3, 2026, 8:04 p.m. |
Created at: May 3, 2026, 4:05 p.m.