Triple
T37172242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Osvald |
E920945
|
entity |
| Predicate | secretNameFor |
P16531
|
FINISHED |
| Object | members of the Osvald Group |
—
|
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: members of the Osvald Group | Statement: [Osvald, secretNameFor, members of the Osvald Group]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secretNameFor Context triple: [Osvald, secretNameFor, members of the Osvald Group]
-
A.
secretDetail
Indicates that one entity reveals or contains confidential or hidden information about another entity or situation.
-
B.
givenNameFor
chosen
Indicates that one entity is the personal first name assigned to or used for another entity.
-
C.
secretedBy
Indicates that a substance or product is released or produced by a particular cell, tissue, organ, or organism.
-
D.
keepsSecretAbout
Indicates that one entity intentionally withholds or conceals information regarding another specified entity or topic from others.
-
E.
secretOrPublic
Indicates whether something is kept confidential or made openly accessible to others.
- 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_69f76ea16f288190b445aa1604d996f4 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb55de3b9c8190a7656aeab3c3ffbc |
completed | May 6, 2026, 2:53 p.m. |
| PD | Predicate disambiguation | batch_69fb35bc92e08190bff447624e2df791 |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 3, 2026, 4:15 p.m.