Triple
T27891998
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Delegates (Indian chamber) |
E705378
|
entity |
| Predicate | segregatedBy |
P127401
|
FINISHED |
| Object | race |
—
|
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: race | Statement: [House of Delegates (Indian chamber), segregatedBy, race]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: segregatedBy Context triple: [House of Delegates (Indian chamber), segregatedBy, race]
-
A.
segregatedFor
Indicates that one entity is separated or set apart from others specifically for the use, benefit, or association of another entity.
-
B.
segregatedIn
chosen
Indicates that one entity is separated or isolated within a specific space, group, or context defined by another entity.
-
C.
separatesBy
Indicates that one entity divides, partitions, or creates a boundary between two or more other entities.
-
D.
separatedIn
Indicates that two or more entities, once together or associated, have been divided, split, or otherwise placed into distinct parts, groups, or locations.
-
E.
segregatedRepresentation
Indicates that the representation of entities is separated into distinct groups or categories, rather than being combined or integrated.
- 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_69ef96b39c448190a9b3aa6672a5168f |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f639b6405081908f52f931b59520ef |
completed | May 2, 2026, 5:51 p.m. |
| PD | Predicate disambiguation | batch_69f6318be69481909d1bcf29b7b60eb2 |
completed | May 2, 2026, 5:17 p.m. |
Created at: April 27, 2026, 6:36 p.m.