Triple
T1908134
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St. Augustine movement |
E38048
|
entity |
| Predicate | hadKeyEvent |
P811
|
FINISHED |
| Object | demonstrations at the Monson Motor Lodge |
—
|
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: demonstrations at the Monson Motor Lodge | Statement: [St. Augustine movement, hadKeyEvent, demonstrations at the Monson Motor Lodge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadKeyEvent Context triple: [St. Augustine movement, hadKeyEvent, demonstrations at the Monson Motor Lodge]
-
A.
hasKeyEvent
chosen
Indicates that an entity includes, is associated with, or is characterized by a significant or defining event.
-
B.
hasKeyboard
Indicates that one entity possesses or is equipped with a keyboard as a component or accessory.
-
C.
hasKeyActivity
Indicates that an entity is associated with or performs a primary or central activity.
-
D.
hadEvent
Indicates that an entity experienced, hosted, or was associated with a specific event at some point in time.
-
E.
hadListeningEventAt
Indicates that a listening event involving an entity occurred at a specific time or place.
- 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_69a8862a26088190aae5243695aeefc0 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb34d94fc8190a5bf1e582c77c725 |
completed | March 7, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69abafeba3d88190afcce67483d8625b |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:35 p.m.