Triple
T3361578
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grand Tyler |
E70732
|
entity |
| Predicate | locationDuringMeetings |
P8904
|
FINISHED |
| Object | outside the closed lodge door |
—
|
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: outside the closed lodge door | Statement: [Grand Tyler, locationDuringMeetings, outside the closed lodge door]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationDuringMeetings Context triple: [Grand Tyler, locationDuringMeetings, outside the closed lodge door]
-
A.
hasMeetingLocation
chosen
Indicates that an entity (such as a meeting or event) takes place at or is associated with a specific location.
-
B.
locationOfLaterMeeting
Indicates the place where a subsequent or future meeting is scheduled or expected to occur.
-
C.
meetingPlaceTerritory
Indicates the territory or geographic area where a meeting or gathering takes place.
-
D.
previousMeetingPlace
Indicates the location where two or more entities met on a prior occasion.
-
E.
meetsVia
Indicates that two entities come into contact or interact with each other through a specified intermediary medium, channel, or mechanism.
- 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_69ad85a660c48190998489309a3b4869 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb26906948190851a7b7d543a4d64 |
completed | March 8, 2026, 5:31 p.m. |
| PD | Predicate disambiguation | batch_69ada4317e288190ab7d0f66e9dba65f |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:13 p.m.