Triple
T15908519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince Humperdinck |
E385785
|
entity |
| Predicate | plansEvent |
P75015
|
FINISHED |
| Object | marriage to Buttercup |
—
|
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: marriage to Buttercup | Statement: [Prince Humperdinck, plansEvent, marriage to Buttercup]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plansEvent Context triple: [Prince Humperdinck, plansEvent, marriage to Buttercup]
-
A.
plansMeetingWith
Indicates that one entity arranges or intends to organize a meeting involving another entity.
-
B.
event
Indicates that there exists an occurrence or happening involving one or more entities, typically situated in time and possibly space.
-
C.
eventManagement
chosen
Indicates the organization, coordination, and oversight of all activities and resources involved in planning and executing an event.
-
D.
eventUse
Indicates that an event involves the use or utilization of a particular entity (e.g., a resource, tool, or method) as part of its occurrence.
-
E.
proposesEvent
Indicates that one entity suggests or puts forward an event for consideration, planning, or approval 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_69d86da686e4819097cbf3b1fc2d881d |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e17d4d08f481909f38b75e3f42d9ab |
completed | April 17, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69e142ca3b208190946c3aa4c1e6087c |
completed | April 16, 2026, 8:12 p.m. |
Created at: April 10, 2026, 4:52 a.m.