Triple
T28735234
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | England |
E730779
|
entity |
| Predicate | containsBody |
P131753
|
FINISHED |
| Object | House of Commons |
—
|
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: House of Commons | Statement: [England, containsBody, House of Commons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsBody Context triple: [England, containsBody, House of Commons]
-
A.
hasBodyOf
Indicates that one entity possesses, contains, or is composed of the physical body or main substance of another entity.
-
B.
haveBody
chosen
Indicates that one entity possesses, contains, or is associated with another entity as its body or main physical/content component.
-
C.
usesBody
Indicates that one entity employs or utilizes the physical body of another (or its own) as a means or instrument to perform an action or function.
-
D.
requiresBody
Indicates that one entity cannot exist, function, or be valid without being associated with or contained within another entity that serves as its body.
-
E.
hasBodyCount
Indicates that an entity is associated with a specific number of deaths or kills.
- 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_69f043eae0908190b28ce314686247d7 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69fdbc5ef46c8190bbcfb9798f4615b7 |
completed | May 8, 2026, 10:35 a.m. |
| PD | Predicate disambiguation | batch_69fdbb270338819082ce3f73903e884f |
completed | May 8, 2026, 10:29 a.m. |
Created at: April 28, 2026, 6 a.m.