Triple
T7112138
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shepard–Byrd Act |
E165730
|
entity |
| Predicate | extendsProtectionBeyond |
P9292
|
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: [Shepard–Byrd Act, extendsProtectionBeyond, race]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: extendsProtectionBeyond Context triple: [Shepard–Byrd Act, extendsProtectionBeyond, race]
-
A.
expandedProtectionTo
chosen
Indicates that an existing protection, safeguard, or coverage was broadened to include an additional entity, group, area, or scope.
-
B.
addsProtectionFor
Indicates that one entity provides or increases protective measures or safeguards for another entity.
-
C.
extendsBeyond
Indicates that one entity continues past or surpasses the spatial, temporal, or conceptual limits of another entity.
-
D.
extendedBy
Indicates that one entity builds upon, enlarges, or adds to the scope, functionality, or duration of another entity.
-
E.
extendedIn
Indicates that one entity continues, prolongs, or expands the scope, duration, or range of another entity.
- 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_69c6888120f081908f8f01b201dc4a4c |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e5edf89c8190a069b35ff7768165 |
completed | March 27, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c4f9788190830288d00cc37026 |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:43 p.m.