Triple
T5098612
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Law of Suspects |
E114926
|
entity |
| Predicate | approximateEndOfUse |
P6544
|
FINISHED |
| Object | 1794 |
—
|
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: 1794 | Statement: [Law of Suspects, approximateEndOfUse, 1794]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateEndOfUse Context triple: [Law of Suspects, approximateEndOfUse, 1794]
-
A.
approximateEndUse
Indicates that something is an estimated or inferred final purpose, application, or consumption context of another entity.
-
B.
timePeriodEndApprox
Indicates that the associated time period ends at an approximate, rather than exact, point in time.
-
C.
usedUntil
chosen
Indicates that something remained in use or operation up to a specified time or event, after which it was no longer used.
-
D.
endTimeApproximate
Indicates that the recorded end time of an event or action is not exact but an approximate value.
-
E.
typicalEndDate
Indicates the date on which something, such as an event, process, or period, normally or customarily ends.
- 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_69bd443fc49c819089629c00e311310c |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd7567d21081909227ed8f08b74c71 |
completed | March 20, 2026, 4:27 p.m. |
| PD | Predicate disambiguation | batch_69bd715e06808190931934dc9930f997 |
completed | March 20, 2026, 4:10 p.m. |
Created at: March 20, 2026, 1:40 p.m.