Triple
T11082114
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | James McKay |
E262022
|
entity |
| Predicate | engagementContext |
P70999
|
FINISHED |
| Object | visits fiancée’s family ranch |
—
|
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: visits fiancée’s family ranch | Statement: [James McKay, engagementContext, visits fiancée’s family ranch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: engagementContext Context triple: [James McKay, engagementContext, visits fiancée’s family ranch]
-
A.
engagementOf
Indicates a relationship where an engagement, commitment, or formal involvement is associated with or attributed to a specific entity.
-
B.
engagementEnvironment
chosen
Indicates the situational context or setting in which an interaction, activity, or engagement takes place.
-
C.
engagementStart
Indicates the point in time or event at which an engagement, interaction, or formal involvement between parties begins.
-
D.
engagementTo
Indicates a formal promise or commitment between two entities to enter into a future partnership or binding relationship.
-
E.
engagementType
Indicates the specific kind or category of engagement or interaction that occurs between the related entities.
- 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_69d6aa9983c08190b0ef61603b69feac |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d799985650819089b2c0f35a212414 |
completed | April 9, 2026, 12:20 p.m. |
| PD | Predicate disambiguation | batch_69d74415403c81909778bcd829e8832e |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:27 p.m.