Triple
T34314634
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 99-603 |
E880542
|
entity |
| Predicate | setsCutoffDate |
P160736
|
FINISHED |
| Object | presence in the United States since before 1982 |
—
|
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: presence in the United States since before 1982 | Statement: [99-603, setsCutoffDate, presence in the United States since before 1982]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setsCutoffDate Context triple: [99-603, setsCutoffDate, presence in the United States since before 1982]
-
A.
cutoffDateForInclusion
chosen
Indicates the date after which items are no longer considered eligible to be included in a given set, process, or evaluation.
-
B.
setsTermEndDateFor
Indicates setting or assigning the end date of a term or period for another entity.
-
C.
hasCutoffTime
Indicates that there is a specific time limit or deadline by which an action, event, or process must be completed or initiated.
-
D.
cutOffDateYear
Indicates the calendar year that serves as the cutoff point beyond which something no longer applies, is valid, or is considered.
-
E.
endDate
Indicates the point in time at which an event, state, or relationship stops being valid or comes to a conclusion.
- 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_69f349b8bb6c8190ad12a7957a574f04 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f717836f0c8190b4a397bbac37dd09 |
completed | May 3, 2026, 9:38 a.m. |
| PD | Predicate disambiguation | batch_69f7127a2ff08190b77d00963c9df621 |
completed | May 3, 2026, 9:16 a.m. |
Created at: May 1, 2026, 1:57 a.m.