Triple
T340101
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Otto Laporte Lecture |
E6814
|
entity |
| Predicate | presentationType |
P7148
|
FINISHED |
| Object | lecture |
—
|
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: lecture | Statement: [Otto Laporte Lecture, presentationType, lecture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: presentationType Context triple: [Otto Laporte Lecture, presentationType, lecture]
-
A.
presentedIn
Indicates that something is shown, displayed, or formally introduced within a particular context, medium, event, or setting.
-
B.
presentedBy
Indicates that something (such as an event, performance, or work) is formally organized, hosted, or introduced by a particular person or entity.
-
C.
conferenceFormat
Indicates the type or structure in which a conference is organized or conducted (e.g., in-person, virtual, hybrid, workshop-based).
-
D.
conferenceType
Indicates the specific category or kind of conference associated with an entity (e.g., workshop, symposium, seminar).
-
E.
displayType
chosen
Indicates the manner or format in which something is presented, shown, or rendered.
- 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_69a2e7951ba08190960e90823b5078f3 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2eae4fcc08190bd4c2bf0149c8b50 |
completed | Feb. 28, 2026, 1:17 p.m. |
| PD | Predicate disambiguation | batch_69a2e95067e88190a914a1c1d0283dfc |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.