Triple
T26792723
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ron Franz |
E670558
|
entity |
| Predicate | modeOfMeeting |
P3082
|
FINISHED |
| Object | meets Christopher McCandless while giving him a ride |
—
|
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: meets Christopher McCandless while giving him a ride | Statement: [Ron Franz, modeOfMeeting, meets Christopher McCandless while giving him a ride]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modeOfMeeting Context triple: [Ron Franz, modeOfMeeting, meets Christopher McCandless while giving him a ride]
-
A.
meetingType
chosen
Indicates the specific category or format of a meeting that characterizes how it is organized or conducted.
-
B.
communicationMode
Indicates the method or channel through which communication between entities is carried out.
-
C.
meetingState
Indicates the current status or phase of a meeting within its overall lifecycle (e.g., scheduled, in progress, or completed).
-
D.
meetingLevel
Indicates the degree or intensity of interaction or engagement between participants in a meeting or meeting-like context.
-
E.
meetingNumber
Indicates the specific numerical identifier assigned to distinguish one meeting from others.
- 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_69eeb31d45f8819089f52ebdbc556218 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f619bd27908190ac9152693dd37658 |
completed | May 2, 2026, 3:35 p.m. |
| PD | Predicate disambiguation | batch_69f611ad2eb48190ac1ed0090f13f7a9 |
completed | May 2, 2026, 3:01 p.m. |
Created at: April 27, 2026, 4:17 a.m.