Triple
T15686794
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fourth Address |
E380221
|
entity |
| Predicate | originallyDeliveredAs |
P74956
|
FINISHED |
| Object | public lecture in Berlin |
—
|
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: public lecture in Berlin | Statement: [Fourth Address, originallyDeliveredAs, public lecture in Berlin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originallyDeliveredAs Context triple: [Fourth Address, originallyDeliveredAs, public lecture in Berlin]
-
A.
deliveredAs
Indicates that something is provided, transmitted, or presented in a particular form, manner, or role.
-
B.
originallyPresentedAs
chosen
Indicates that one entity was first introduced, described, or characterized in the form or manner specified by another entity.
-
C.
formerlyDeliveryMode
Indicates that an entity previously used a particular delivery mode but no longer does so.
-
D.
deliveredFrom
Indicates that something has been sent, transported, or provided from a particular source or origin to another party or location.
-
E.
originallyHad
Indicates that an entity previously possessed, contained, or was associated with something before a change, loss, or transformation occurred.
- 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_69d86d99e860819094b6957cde470f2c |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e04f4b73d881908ec0f21393a01969 |
completed | April 16, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69deda8c856c8190882330114f9a1a5f |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:44 a.m.