Triple
T1349526
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | E-Verify |
E28848
|
entity |
| Predicate | hasOnlinePortal |
P57
|
FINISHED |
| Object | E-Verify employer web interface |
—
|
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: E-Verify employer web interface | Statement: [E-Verify, hasOnlinePortal, E-Verify employer web interface]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOnlinePortal Context triple: [E-Verify, hasOnlinePortal, E-Verify employer web interface]
-
A.
hasOnlinePlatform
chosen
Indicates that an entity operates, maintains, or is associated with a presence or service on an online platform.
-
B.
hasOnlineCatalog
Indicates that an entity provides a catalog of its items or offerings that is accessible via the internet.
-
C.
isOfficialPortalFor
Indicates that one entity serves as the recognized, authoritative portal or entry point for accessing information or services related to another entity.
-
D.
hasOnlineCommunity
Indicates that an entity maintains or is associated with a community that interacts primarily through online platforms or digital channels.
-
E.
hasPortico
Indicates that one entity (typically a building or structure) features a portico as part of its architectural design.
- 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.