Triple
T27938253
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fred |
E700669
|
entity |
| Predicate | invitesToChristmasDinner |
P96638
|
FINISHED |
| Object | Ebenezer Scrooge |
—
|
NE NERFINISHED |
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: Ebenezer Scrooge | Statement: [Fred, invitesToChristmasDinner, Ebenezer Scrooge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: invitesToChristmasDinner Context triple: [Fred, invitesToChristmasDinner, Ebenezer Scrooge]
-
A.
invitesParticipationOf
Indicates that one entity actively requests or encourages another entity to take part in an activity, event, or process.
-
B.
invitesToLocation
chosen
Indicates that one entity extends an invitation to another entity to go to or be present at a specific location.
-
C.
isInvited
Indicates that one entity has extended an invitation to another entity to participate in or attend something.
-
D.
invitationPurpose
Indicates that an invitation is extended with a specific intended purpose or reason, linking the invitation to what it is meant to achieve or be used for.
-
E.
guestAtWedding
Indicates that a person is attending or has attended a particular wedding as a guest.
- 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_69ef6a5028108190a14696d9821dde49 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c6895f0819088655277e45859a8 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 7:15 p.m.