Triple
T22003759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Party |
E543397
|
entity |
| Predicate | oftenMeetsAt |
P47991
|
FINISHED |
| Object | Mike Wheeler's basement |
—
|
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: Mike Wheeler's basement | Statement: [The Party, oftenMeetsAt, Mike Wheeler's basement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenMeetsAt Context triple: [The Party, oftenMeetsAt, Mike Wheeler's basement]
-
A.
meetsRegularly
chosen
Indicates that two or more entities come together on a recurring or scheduled basis.
-
B.
meetsVia
Indicates that two entities come into contact or interact with each other through a specified intermediary medium, channel, or mechanism.
-
C.
meetsBy
Indicates that one entity encounters or comes together with another entity, typically at a specific time or place.
-
D.
meetsWhen
Indicates that two entities come together or encounter each other at a specific time or under particular temporal conditions.
-
E.
mayMeetAt
Indicates that two or more entities are permitted or able to have a meeting or encounter at a specified place or time.
- 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_69e11e2c814c8190837d072789000486 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f1276cab5c8190ac1236fde7e0394a |
completed | April 28, 2026, 9:32 p.m. |
| PD | Predicate disambiguation | batch_69e6f62dc9d88190ae387f145f9528de |
completed | April 21, 2026, 3:59 a.m. |
Created at: April 16, 2026, 8:20 p.m.