Triple
T37555154
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Constructs |
E933677
|
entity |
| Predicate | hasNotableUnitType |
P33147
|
FINISHED |
| Object | abominations |
—
|
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: abominations | Statement: [House of Constructs, hasNotableUnitType, abominations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableUnitType Context triple: [House of Constructs, hasNotableUnitType, abominations]
-
A.
includesNotableUnit
Indicates that an entity contains or comprises at least one unit, component, or subpart that is considered notable or significant.
-
B.
hasNotableTeamType
Indicates that an entity is associated with a team that is recognized as having a specific notable type or category.
-
C.
hasNotableType
chosen
Indicates that an entity is associated with a specific notable category or type that characterizes its significance or role.
-
D.
hasNotableNation
Indicates that an entity is significantly associated with or recognized for a particular nation.
-
E.
hasNotableNamesakeType
Indicates that an entity has a notable namesake of a specified type (such as a person, place, or work) that shares its name.
- 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_69f76eca55bc8190acf25741793d5dac |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a1553e08190bb7424c448cb1f33 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:17 p.m.