Triple
T22868990
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oyneg Shabes group |
E567132
|
entity |
| Predicate | archiveHiddenIn |
P68420
|
FINISHED |
| Object | milk cans |
—
|
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: milk cans | Statement: [Oyneg Shabes group, archiveHiddenIn, milk cans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: archiveHiddenIn Context triple: [Oyneg Shabes group, archiveHiddenIn, milk cans]
-
A.
archiveBuriedIn
Indicates that an archive is physically located underground or within a buried structure or site.
-
B.
hiddenIn
chosen
Indicates that one entity is concealed within, behind, or inside another entity so that it is not readily visible or apparent.
-
C.
hiddenAt
Indicates that one entity is concealed or stored at a specific location or within another entity.
-
D.
archiveOf
Indicates that one entity serves as a stored collection or repository preserving the records, documents, or materials of another entity.
-
E.
archiveFor
Indicates that one entity serves as a storage or preservation repository specifically for the records, documents, or data of another entity.
- 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_69e24589d8348190b96422d13a678bc1 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17f0384a88190a0fbf57b5dca8d5a |
completed | April 29, 2026, 3:46 a.m. |
| PD | Predicate disambiguation | batch_69eed2d8c0608190afef4c4e530c0e2c |
completed | April 27, 2026, 3:07 a.m. |
Created at: April 17, 2026, 3:38 p.m.