Triple
T509292
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regent House |
E10569
|
entity |
| Predicate | membershipDeterminedBy |
P7663
|
FINISHED |
| Object | statutory criteria |
—
|
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: statutory criteria | Statement: [Regent House, membershipDeterminedBy, statutory criteria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: membershipDeterminedBy Context triple: [Regent House, membershipDeterminedBy, statutory criteria]
-
A.
membershipDecidedBy
chosen
Indicates that the determination of whether an entity is granted membership in a group, organization, or set is made by another specified entity or process.
-
B.
memberCategory
Indicates that an entity belongs to or is classified under a specific category or group.
-
C.
membershipRequired
Indicates that access to or use of something is conditional on being a member of a specified group or organization.
-
D.
hasMembershipBase
Indicates that an entity possesses or is associated with a foundational group or set of members that form its membership base.
-
E.
membershipPeak
Indicates the time or period at which an entity’s membership in a group or organization reaches its highest level.
- 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_69a2e848adf881908e5e04f7af030093 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f164a9d48190b525a97b5c06ffe2 |
completed | Feb. 28, 2026, 1:45 p.m. |
| PD | Predicate disambiguation | batch_69a2edfe236481909901cc7d4281b33c |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.