Triple
T5128494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Draco Malfoy |
E115637
|
entity |
| Predicate | houseTraitAssociation |
P62698
|
FINISHED |
| Object | ambition |
—
|
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: ambition | Statement: [Draco Malfoy, houseTraitAssociation, ambition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: houseTraitAssociation Context triple: [Draco Malfoy, houseTraitAssociation, ambition]
-
A.
architectureProperty
Indicates that a specified architectural characteristic or feature is attributed to, or associated with, an entity.
-
B.
associatedHouse
Indicates a relationship where one entity is linked or connected to a particular house, typically as its related or corresponding house.
-
C.
estateVariantName
Indicates that one name is an alternative or variant designation used for the same estate.
-
D.
houseInvolved
Indicates that a house plays a significant role or is directly implicated in the specified event, situation, or relationship.
-
E.
roofFeature
Indicates that one entity is a feature, element, or characteristic that is part of or associated with a roof.
- F. None of above. chosen
Provenance (4 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_69bd444426bc819099ccd23f141e22aa |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd7d5a23908190a24e79d1b29d6fcf |
completed | March 20, 2026, 5:01 p.m. |
| PD | Predicate disambiguation | batch_69bd77aa68b88190a50dd736a72d2901 |
completed | March 20, 2026, 4:36 p.m. |
| PDg | Predicate description generation | batch_69bd7d5906d88190b805977e5a05767a |
completed | March 20, 2026, 5:01 p.m. |
Created at: March 20, 2026, 1:42 p.m.