Triple
T9256965
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ryan Sweeting |
E222467
|
entity |
| Predicate | engagementToKaleyCuocoAnnounced |
P59137
|
FINISHED |
| Object | 2013-09 |
—
|
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: 2013-09 | Statement: [Ryan Sweeting, engagementToKaleyCuocoAnnounced, 2013-09]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: engagementToKaleyCuocoAnnounced Context triple: [Ryan Sweeting, engagementToKaleyCuocoAnnounced, 2013-09]
-
A.
engagementAnnouncedBy
Indicates that an engagement (such as a betrothal or formal commitment) is publicly announced or made known by a specific agent or source.
-
B.
engagementTo
chosen
Indicates a formal promise or commitment between two entities to enter into a future partnership or binding relationship.
-
C.
engagementOf
Indicates a relationship where an engagement, commitment, or formal involvement is associated with or attributed to a specific entity.
-
D.
engagementStart
Indicates the point in time or event at which an engagement, interaction, or formal involvement between parties begins.
-
E.
engagedBy
Indicates that an entity is actively involved, occupied, or participating in an activity, process, or interaction initiated or provided by another entity.
- 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_69ca841e4cd481908e738c74e958eaea |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd06b4e2048190af0d65b904677c36 |
completed | April 1, 2026, 11:51 a.m. |
| PD | Predicate disambiguation | batch_69cc7a4e79e48190b3200247f4624867 |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:32 p.m.