Triple
T10516944
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mr. Brocklehurst |
E248057
|
entity |
| Predicate | allowsForFamily |
P94337
|
FINISHED |
| Object | luxurious clothing |
—
|
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: luxurious clothing | Statement: [Mr. Brocklehurst, allowsForFamily, luxurious clothing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allowsForFamily Context triple: [Mr. Brocklehurst, allowsForFamily, luxurious clothing]
-
A.
containsFamily
Indicates that one entity includes or encompasses members of a particular family group within it.
-
B.
usedByFamily
Indicates that something is regularly utilized or consumed by a family as a group.
-
C.
eligibleFamily
Indicates that one entity qualifies as a family member of another under specified eligibility rules or criteria.
-
D.
belongsToFamily
Indicates that an entity is a member of, or is associated as part of, a specific family group.
-
E.
possibleFamily
Indicates that two entities could plausibly be related as members of the same family, though the familial relationship is not confirmed.
- 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_69d381c4aa948190942e1d803143fb0e |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d509cc58b081908ef15aa89b396db6 |
completed | April 7, 2026, 1:42 p.m. |
| PD | Predicate disambiguation | batch_69d4fb94fa10819091f585bab4379c6f |
completed | April 7, 2026, 12:41 p.m. |
| PDg | Predicate description generation | batch_69d4fe06d4a48190b1a45dd1d4e16df0 |
completed | April 7, 2026, 12:52 p.m. |
Created at: April 6, 2026, 12:28 p.m.