Triple
T20820640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edwin Jarvis |
E512562
|
entity |
| Predicate | householdDuties |
P68145
|
FINISHED |
| Object | maintaining Avengers Mansion |
—
|
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: maintaining Avengers Mansion | Statement: [Edwin Jarvis, householdDuties, maintaining Avengers Mansion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: householdDuties Context triple: [Edwin Jarvis, householdDuties, maintaining Avengers Mansion]
-
A.
householdPractice
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.
householdStaff
chosen
Indicates that one entity serves as domestic or household staff for another entity, typically within a private residence.
-
E.
homeWork
Indicates that one entity assigns, has, or is responsible for homework in relation to 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_69e0b4ce39108190a6e8e5df4f1c8dc5 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c2f7a1548190b6ef3f1cfad37c1c |
completed | April 21, 2026, 12:21 a.m. |
| PD | Predicate disambiguation | batch_69e5c99ca55481908e8d434fa901cfd6 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:41 p.m.