Triple
T32607880
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Medallion Lectures |
E833571
|
entity |
| Predicate | areHeldAt |
P174643
|
FINISHED |
| Object | major IMS meetings |
—
|
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: major IMS meetings | Statement: [Medallion Lectures, areHeldAt, major IMS meetings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: areHeldAt Context triple: [Medallion Lectures, areHeldAt, major IMS meetings]
-
A.
areHeldIn
Indicates that events, activities, or objects take place or are located within a particular venue, container, or setting.
-
B.
isHeldAt
Indicates that an event, state, or condition occurs or is in effect at a specific time or temporal point.
-
C.
heldAtLocation
Indicates that an entity is being kept or stored at a specific location.
-
D.
isUsuallyHeldBy
Indicates that something is most commonly or typically possessed, carried, or controlled by a particular entity.
-
E.
sometimesHeldBy
Indicates that one entity is occasionally or intermittently possessed, owned, or physically held by another entity, but not on a constant or permanent basis.
- 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_69f3492bfa648190b6ae472074634e29 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6c6c80a388190b038cfe32c2f2ca4 |
completed | May 3, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2c138481908afa3ee3e91f8900 |
completed | May 3, 2026, 3:12 a.m. |
| PDg | Predicate description generation | batch_69f6c2df27ec8190912ec8eb488836d0 |
completed | May 3, 2026, 3:37 a.m. |
Created at: May 1, 2026, 1:05 a.m.