Triple
T27937635
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fred (Scrooge’s nephew) |
E700654
|
entity |
| Predicate | householdActivity |
P27135
|
FINISHED |
| Object | hosts Christmas party |
—
|
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: hosts Christmas party | Statement: [Fred (Scrooge’s nephew), householdActivity, hosts Christmas party]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: householdActivity Context triple: [Fred (Scrooge’s nephew), householdActivity, hosts Christmas party]
-
A.
householdPractice
chosen
Indicates a relationship where an entity engages in or carries out a particular practice, behavior, or routine within the context of a household.
-
B.
household
Indicates that two or more entities belong to or are part of the same household unit, typically sharing a residence and domestic life.
-
C.
householdCenter
Indicates the central location or primary focal point associated with a particular household.
-
D.
typicalActivity
Indicates that an entity is commonly or characteristically engaged in a particular activity.
-
E.
housesWork
Indicates that one entity serves as the location or facility where another entity’s work or activities are based or carried out.
- 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_69f65876c52c8190bc889c7a67bd07f3 |
completed | May 2, 2026, 8:03 p.m. |
| PD | Predicate disambiguation | batch_69f6575d89788190aca478e4aea05a65 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 27, 2026, 7:14 p.m.