Triple
T1349516
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | E-Verify |
E28848
|
entity |
| Predicate | verificationTimeframe |
P2796
|
FINISHED |
| Object | after hire and within three business days of employee start date |
—
|
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: after hire and within three business days of employee start date | Statement: [E-Verify, verificationTimeframe, after hire and within three business days of employee start date]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: verificationTimeframe Context triple: [E-Verify, verificationTimeframe, after hire and within three business days of employee start date]
-
A.
commitmentTiming
chosen
Indicates the point in time or period relative to an event or agreement when a commitment is made, becomes effective, or is expected to be fulfilled.
-
B.
timeOfAttestation
Indicates the specific time at which a statement, document, or claim is formally attested or verified.
-
C.
visibilityDuration
Indicates the length of time for which something remains visible or observable.
-
D.
locationPeriod
Indicates that an entity is associated with being at a particular location during a specified time period.
-
E.
documentationPeriod
Indicates the time span or interval during which something is documented, recorded, or valid in the documentation.
- 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_69a498571d248190a0ac9eb02d97097f |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c268745481908be649526c18e558 |
completed | March 1, 2026, 10:49 p.m. |
| PD | Predicate disambiguation | batch_69a4bef5857c81909ae984feb85a26ca |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:56 p.m.