Triple
T2446631
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fugitive Slave Act of 1850 |
E53608
|
entity |
| Predicate | inEffectUntil |
P2110
|
FINISHED |
| Object | 1864 |
—
|
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: 1864 | Statement: [Fugitive Slave Act of 1850, inEffectUntil, 1864]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inEffectUntil Context triple: [Fugitive Slave Act of 1850, inEffectUntil, 1864]
-
A.
inForceUntil
chosen
Indicates that a condition, rule, or agreement remains valid and operative up to a specified time or event.
-
B.
governsUntil
Indicates that one entity exercises governing authority or control over another entity up to, but not beyond, a specified time or condition.
-
C.
delayedUntil
Indicates that the occurrence or effect of one event or condition is postponed and does not take place until a specified later event, time, or condition is reached.
-
D.
usedUntil
Indicates that something remained in use or operation up to a specified time or event, after which it was no longer used.
-
E.
basedInUntil
Indicates that an entity was based or located in a particular place up to a specified end time or date, after which this association ceased.
- 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_69ab495d227c8190b26ae6548eeb1019 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abcabf477081908512df63ac1a6414 |
completed | March 7, 2026, 6:50 a.m. |
| PD | Predicate disambiguation | batch_69abc5ad8e588190b97c4cd7cf575043 |
completed | March 7, 2026, 6:29 a.m. |
Created at: March 6, 2026, 9:43 p.m.